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 <akr / fsij.org> wrote:

> 2013/7/10 tenderlovemaking (Aaron Patterson) <aaron / tenderlovemaking.com>:
> > 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.
>
>