 |
 |
After some observations, I think the reason stems from creating the proxy in a non-standard location (different from /tmp/x509up_u<user_id>) via voms-proxy-init <COMMANDS> --out <NON_STANDARD_LOCATION> If a new process is forked where this proxy will be used then an environmental variable X509_USER_PROXY should be set in that process like this: export X509_USER_PROXY=<NON_STANDARD_LOCATION> If this environmental variable is not set, then the proxy will be looked for in the standard location /tmp/x509up_u<user_id> where it might not even exist. I am not so sure if voms-proxy-init --noregen should also be supplied for that process. Some of my other troubles posted in other threads could also be linked to creating the proxy in a non-standard location. Viesturs --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/283#issuecomment-137615658 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1