Thanks for looking into it. If it cannot be replicated by others, then I suppose it's not an issue. Unfortunately I don't have enough administrative clout to do any further testing or reconfiguration. If I were to burn the karma to bug my admin, I'd simply ask him to upgrade the version and hope for the best :) -Chase On Fri, May 13, 2016 at 4:12 PM, Andrew Hanushevsky < [log in to unmask]> wrote: > I have tried this in 4.2.2 as well as 4.3.0 as the server. I tried xrdcp > at 4.3.0 and 4.2.3 (there is no 4.3.2 so I assume it was a digit swap). In > each case, terminating the copy before the close occurred caused the file > to be deleted at the server. If this is still an issue, please forward a > server log file with the server started in debug mode (i.e. -d command line > option) that includes a copy that did not get to actually close the file. I > simply cannot reproduce this problem. > > — > You are receiving this because you authored the thread. > Reply to this email directly or view it on GitHub > <https://github.com/xrootd/xrootd/issues/306#issuecomment-219180880> > --- 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/306#issuecomment-219568649 ######################################################################## 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