> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Stephen Burke
>
> Testbed Support for GridPP member institutes [mailto:TB-
> > [log in to unmask]] On Behalf Of David Grellscheid said:
> > Thanks, Mingchao, for this explanation. I still don't see where in
> > this sequence the VOMS part of the proxy comes in? The proxy renewal
> > itself usually works fine, but the VOMS extension does not get renewed.
>
> Once the bare proxy has been fetched from myproxy the renewal daemon does
> the equivalent of "voms-proxy-init --voms <vo> --noregen" -
>
What renewal demon? Is this a CE component? And how (if at all)
does the regenerated proxy make it to the worker node?
I'm far from sure, but I'm getting the impression that the auto
renewal stuff only ever gets the renewed proxy as far as the CE,
which might be OK for handing back the output sandbox of a long-
running jobs, but does the job no good at all if it does (say)
lcg-cr on the worker node.
Ewan
|