On Wed, 22 Jun 2005, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Daniel Eischen <[EMAIL PROTECTED]> writes: > : We do protect the malloc lock across a fork(), but that's it. > > With 4.x libc_r, you could easily get hangs accross a fork() if you > did anything before the exec (like setup fd's for stdin/out). This > was due to internal libc_r state being inconsistant.
I was only referring to libpthread in the above... I don't think libc_r is as robust in that regard. -- DE _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
