 |
 |
Since last night something got messed up in xrcdp logging. This command (which is expected to fail): xrdcp -f -np -d 1 root://uct2-int.mwt2.org:1094//atlas/dq2/user/ivukotic/xrootd/user.ivukotic.xrootd.mwt2/user.ivukotic.xrootd.unexisting-1M - > /dev/null 2>>upstreamFrom_MWT2_2014-01-13T1801.log & produces output full of null characters. When output is not redirected to a file everything looks OK. The same happens when I log in to lxplus with a clean environment. Doing gymnastics like this: xrdcp -f -np -d 1 root://uct2-int.mwt2.org:1094//atlas/dq2/user/ivukotic/xrootd/user.ivukotic.xrootd.mwt2/user.ivukotic.xrootd.unexisting-1M - 2>&1 >/dev/null | cat >upstreamFrom_MWT2_2014-01-13T1801.log avoids the problem but that's not a nice thing to do. --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/71 ######################################################################## 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