Re: kern/42772 -- pthread issue with fork()

[Michael Graff <explorer%flame.org@localhost>]

On 3/24/10 3:32 PM, Joerg Sonnenberger wrote:
>> Consider the method to become a daemon, you fork() then let the child
>> continue.  Surely we're not saying you cannot use pthread_create() there...
> 
> You are confusing something here. The constraints apply to
> multi-threaded programs. Most daemons do the double-fork dance early and
> start threads afterwards.

True.

Ruby seems to be executing some tests in a forked multithreaded
environment.  I have no reason to believe they are doing anything that
isn't prepared to handle a totally new, blank pthread-allowing environment.

However, even with this patch (which I am about to commit to current) is
not perfect, but it is at least a large chunk of the problem.)

--Michael