On 17/11/11 17:21, Stuart Purdie wrote:
> On 17 Nov 2011, at 17:02, Daniela Bauer wrote:
>
>> Currently they mostly get away with a 24 h proxy made like this:
>> voms-proxy-init -valid 24:00 --voms vo.londongrid.ac.uk
>>
>> Unfortunately some of the jobs need more time, either because they
>> queue for a while or because they've hit a particularly exciting bit
>> of phase space.
>
> Are you sure you can't just create a longer proxy? MyProxy is ok for what it does, but it's another layer of complications, and therefore more things that can go wrong. For a big VO, that's often a good trade off, but for a smaller VO, sometimes simplicity is better. Infrequent users don't really get much of a penalty for longer proxies too.
>
> If memory serves, at one point the default maximum VOMS attribute length was 4 days, so you might well find that you can have a VOMS proxy that long. Note that you'll need to examine the VOMS attributes separatly for the main proxy expiry, because they have a _separate_ lifetime set on them.
>
> Try asking for a long lived ( e.g. 7 days) voms proxy, and see what the voms-attributes length end up as. That's as long as it'll go. If it's 48 hours, that might just be enough, whilst keeping it simple.
We need a recipe for this - I've been asked by snoplus how to do this.
Chris
|