Yukihiro Matsumoto
10/7/2008 7:00:00 AM
Hi,
In message "Re: Ruby lacks atfork : The evil that lives in fork..."
on Tue, 7 Oct 2008 09:41:55 +0900, John Carter <john.carter@tait.co.nz> writes:
|The problem with "don't mix threads with processes" is unless you
|inspect the source code of each version of each library in turn... it
|is very hard to prove that nothing in your system is using a thread
|and a process together.
The point is not to touch thread related objects from the forked child
process. They won't work as expected anyway. It's not too hard to
do, I believe. You were touching them in your example.
matz.