From: Evan Phoenix Date: 2013-07-10T10:30:35+09:00 Subject: [ruby-core:55894] Re: [ruby-trunk - Bug #8616][Open] Process.daemon messes up threads --e89a8fb1ede24c173404e11e3900 Content-Type: text/plain; charset=ISO-8859-1 No, it shouldn't raise an exception. Process.daemon and fork both use after_fork() in C. That function should iterate all the threads and mark them as KILLED since they are all dead. On Tue, Jul 9, 2013 at 6:14 PM, Tanaka Akira wrote: > 2013/7/10 tenderlovemaking (Aaron Patterson) : > > Bug #8616: Process.daemon messes up threads > > https://bugs.ruby-lang.org/issues/8616 > > Process.daemon cannot preserve threads because > it uses fork and fork doesn't copy other threads. > > Maybe, Process.daemon should raise an exception when > multi threads. > > --e89a8fb1ede24c173404e11e3900 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
No, it shouldn't raise an exception. Process.daemon an= d fork both use after_fork() in C. That function should iterate all the thr= eads and mark them as KILLED since they are all dead.


On Tue, Jul 9, 2013 at 6:14 PM, Tanaka A= kira <akr@fsij.org> wrote:
2013/7/10 tenderlovemaking (Aaron Patterson) <aaron@tenderlovemaking.com>:
> Bug #8616: Process.daemon messes up threads
> h= ttps://bugs.ruby-lang.org/issues/8616

Process.daemon cannot preserve threads because
it uses fork and fork doesn't copy other threads.

Maybe, Process.daemon should raise an exception when
multi threads.


--e89a8fb1ede24c173404e11e3900--