> possibly if you go over the maximum (which I
> guess is 96 hours) it falls back to the default (12)?
Actually I think there's a bug here. The man page for voms-proxy-init
says:
-vomslife H Tries to get a pseudo cert with information valid
for H
hours. The default is "as long as the proxy certificate". The
special
value 0 means as long as the server will allow.
but in fact without the vomslife parameter it seems to always give me 12
hours - with the vomslife it works:
voms-proxy-init --voms atlas --hours 95 -vomslife 95:0
[...]
=== VO atlas extension information ===
VO : atlas
subject : /C=UK/O=eScience/OU=CLRC/L=RAL/CN=stephen burke
issuer : /DC=ch/DC=cern/OU=computers/CN=lcg-voms.cern.ch
attribute : /atlas/Role=NULL/Capability=NULL
attribute : /atlas/lcg1/Role=NULL/Capability=NULL
timeleft : 94:59:57
rpm -qf `which voms-proxy-init`
glite-security-voms-clients-1.7.16-2
Stephen
|