 |
 |
Hi Alex,
This is actually not he right place to post this issue as it is an operational problem not an xrootd systemic problem. I would think there is a cms specific mailing list where this question should be posted.
That said, the reason you got a "file exists" error is because the previous failed copy left a partial file in the destination directory. Without the '-f' option, that file cannot be replaced as a protection against over writing an existing file. Otherwise, it looks like there are problems with host xrootd-cms.infn.it.
Andy
—
Reply to this email directly or view it on GitHub.
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