In message <913bf9$qtp$1 / nnrp1.deja.com>
artevo / hotmail.com writes:

> Who has experience in fork and multythreading or can tell a good url or book
> for further information about problems and solutions in this?

That's the topic recently discussed on ruby-list and ruby-dev ---
MLs in Japanese.  Currently all threads are duplicated on fork, and it
sometimes causes a problem.  However kill all threads but which issued
fork may break some library or applications.

There is a somewhat reasonable proposal posted by matz.

  1. Add an argument indicates whether the thread will be killed or
     not to Thread.new.
  2. That argument indicates `kill the thread' in default.

  # eg. something like Thread.new(kill_on_fork = true).

And comments, request, claim, or something else are wanted.

Your proposal may be included in future Ruby standard :-)


-- 
kjana / os.xaxon.ne.jp                              December 12, 2000
It is never late to mend.