Unfortunately, it is not a trivial issue. The problem is that whenever
fork() is called the currennt connections in the parent are destroyed
making it impossible for the parent to continue execution in the current
context without getting a SEGV. The connections in the child are also
destroyed. Whether that's questionable as well. Does the child process
expect to reuse open connections created by the parent? If not, a fix may
be possible. Otherwise, it's rather complicated to fix this.
The main question is "what context does the child process expect?". It's
clear from the way programs are written, the parent process expects
established connections to still be alive. What does the child process
expect?
Andy
On Fri, 19 Jun 2015, Lukasz Janyst wrote:
> That's kind of surprising, given how much you pushed for it, but it means that it is probably a trivial issue. Happy debugging :)
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/244#issuecomment-113646728
—
Reply to this email directly or view it on GitHub.
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
