Follow-up Comment #3, bug #97269 (project xrootd):
The problem is that unlocking fails in child with EPERM, meaning that the
current thread does not own the mutex. This happens even though the POSIX man
page states:
The expected usage is that the prepare handler acquires all mutex locks and
the other two fork handlers release them.
Mea culpa, I haven't tested because it seemed trivial. Never trust the
documentation!
The fix is to destroy and reinitialize the mutex in the child. I will see how
I can do this without interrupting other things.
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?97269>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
########################################################################
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
