Follow-up Comment #1, bug #78973 (project xrootd):
Actually you can flip the flag with both the shell environment and by saying:
EnvPutInt(NAME_ENABLE_FORK_HANDLERS, 1/0). The shell environment setting (if
present) takes precedence.
The reason for disabling it by default is mainly backward compatibility. The
fork handlers shut down the connection manager before the fork (breaking all
the connections), and reinitialize it afterwards. This is not really the best
solution but the only one that could have been reasonably implemented under
the current circumstances. This disturbs the code that used the xrootd client
in the parent process and forked for different purposes (the fork/execve case)
or didn't use the client in the parent process (the proof problem that you
have just hit).
I will add the additional check suggested by Chris.
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?78973>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
