 |
 |
At the risk of asking a stupid question: why is xrdcp able to transfer the file's content with the correct file size? I may be missing something, but dCache's embedded xrootd client and xrdcp are (in essence) doing the same thing: downloading a file. The difference is that xrdcp writes the correct number of bytes to disk while dCache's embedded client writes the wrong file size. If RAL's data server is somehow "wrong" (sending a final response with kXR_oksofar and some bogus response with kXR_ok) why does the transfer work for xrdcp? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1454#issuecomment-894164785 ######################################################################## 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