Hi. Thanks for the information Andy. I realised that my proposed mechanism whereby our server stopped showing errors [the idleScan clearing the situation] doesn't quite fit with the logs: I had better understand and/or reproduce this aspect too, if there's something not understood about what has happened I think it's risky to make a solution. The server is still running, a core image would be ideal but this is part of the production service so things are delicate [i.e. not impacting anyone], of course. I'll update this issue when I can, probably not before next week though.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1928#issuecomment-1441404708", "url": "https://github.com/xrootd/xrootd/issues/1928#issuecomment-1441404708", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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