We seem to be able to trigger it pretty regularly which is forcing us to spend our time dropping the spurious .*.log on a daily base. Now this statistic makes me think that it's not only bad luck that we restart xrootd in between the -p check and the echo statement. I believe that every single restart of xrootd triggers triggers log rotation somehow (or at least some equivalent code) and that we thus have a race condition during the restart. Anyway, it would be nice to fix this as soon as possible as it makes the administration of large xrootd clusters a real pain. --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/302#issuecomment-173492396 ######################################################################## 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