Reply to this email directly or view it on GitHub.
Hi,
I'm using xrdcp client v4.2.3. Is it possible to continue running in the case of errors (specifically, when running in --recursive mode)? The two scenarios where I find this would be useful are:
You have 1000+ large files in some directory, that you'd like to copy. So you spin up xrdcp in a tmux session and let it go overnight.
If there is an error for some reason (e.g. [ERROR] Received corrupted data) on say, file number 5, you're hosed (and not very happy in the morning). This is because currently xrdcp just calls it quits and doesn't even try to transfer the remaining 994 files.
Sometimes I add new data to a directory somewhere, and want to sync that to xrootd, again using the --recursive option. Currently xrootd will quit at the first file that it encounters which already exists at the destination. It would be useful if you could ask it to simply skip these files, and only transfer the new ones.
This could even be a less general case of allowing errors, e.g. by adding a --skipexisting option.
—
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