 |
 |
There were some changes regarding how certain events are processed which was causing other problems. That may have inverted some locks. Next time this happens, could you get a gcore? This kind of stuff is hard to reproduce. We really need to know who has that lock because it will likely lead to the code path that's causing the problem. -- 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/526#issuecomment-307632979 ######################################################################## 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