Hi Albert, That's correct, in case of third-party-copy with delegation we optimized away opening of the source and setting up the rendex-vous as the destination is now able to proceed on its own. Cheers, Michal ________________________________ From: [log in to unmask] [[log in to unmask]] on behalf of Albert Rossi [[log in to unmask]] Sent: 09 May 2019 16:11 To: xrootd-dev Cc: Dmitry Litvintsev Subject: delegation and the tpc.key Hi everyone, I have noticed something interesting about the behavior of the xrootd server/client on TPC with 4.9. I had not noticed this before because I had not looked at verbose debug output, since everything seemed to be working. What I notice is the following: 1. Where before the client (xrdcp) used to do an open on the source again during the copy phase, I no longer see this occurring. 2. At the same time, the destination server (i.e., the server-side xrdcp client) does not pass the tpc.key to the source server on open. I noticed this because my own logging was reporting "not a tpc open" at that point. Everything is working fine, but I just wanted to make sure what I am seeing is correct. Am I correct in concluding that if delegation has occurred, the xrootd server stops using the tpc token? Thanks, Al ________________________________________________ Albert L. Rossi Application Developer & Systems Analyst III Scientific Computing Division, Data Movement Development FCC 229A Mail Station 369 (FCC 2W) Fermi National Accelerator Laboratory Batavia, IL 60510 (630) 840-3023 ________________________________ 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 ######################################################################## 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