From: Tanaka Akira Date: 2005-11-19T00:46:06+09:00 Subject: Re: Problem with Daemon written in ruby... In article <437DE7CF.4000703@shic.co.uk>, "Steve [RubyTalk]" writes: > Should I have expected this? What would be the best way to address the > problem? I don't see why having used fork should have affected > threading. Can anyone explain? 1. fork doesn't copy other threads in the child process. 2. fork+setsid daemonization kills the parent process. So the daemon process has only the thread which calls fork. Process.daemon in Ruby 1.9 may help you. It daemonize the process without killing other threads. -- Tanaka Akira