On Fri, Jun 22, 2007 at 08:51:39AM -0500, Jim Basney wrote: Thanks, I wasn't aware of that.
I was a litte bit confused because aufter logging into our GridWay host via gsissh a grid-proxy-init also produced this 'session enabled filename format'. This happens only due to the $X509_USER_PROXY env. variable which is set by GSI-OpenSSH. After removing the variable from the environment everything works as expected. Best wishes, Thomas > GSI-OpenSSH has always operated this way, to avoid overwriting the > credentials of other active sessions. The standard search algorithm for > proxy files is documented at: > http://www.globus.org/toolkit/docs/4.0/security/prewsaa/Pre_WS_AA_Public_Interfaces.html#prewsaa-env-credentials > GridWay should honor the X509_USER_PROXY environment variable set by > GSI-OpenSSH. > > Thomas Bruesemeister <[EMAIL PROTECTED]> wrote: > > Hi, > > > > we are useing GridWay as a metascheduler in our > > Globus-based grid environment. GridWay expects the proxy > > certificate to be in the form 'x509up_u<uid>'. > > > > When I log into our Gobus machines using gsissh > > the proxy certificate file name changes into > > x509up_p<pid>.file... > > > > e.g. /tmp/x509up_p2341.filetIBbsm.1 > > > > I guess that this was not the case some > > time ago. We rely on the standard x509up_u<uid> > > naming scheme. So my question is what triggers > > this format change and how can we prevent that. > > > > Every help is greatly appreciated. > > > > > > Best wishes, > > -- > > Thomas Bruesemeister > > > > Astronomisches Rechen-Institut > > am Zentrum für Astronomie > > der Universität Heidelberg > > > > Fon: +49 (0)6221 54-1834 > > Fax: +49 (0)6221 54-1888 > > [EMAIL PROTECTED]
