Some operating systems retain the status of terminated child processes
until the parent collects that status (normally using some variant of
wait()
. If the parent never collects this status, the child
stays around as a zombie process. Process::detach
prevents this by setting up a separate Ruby thread whose sole job is to
reap the status of the process pid when it terminates. Use
detach
only when you do not intent to explicitly wait for the
child to terminate.
The waiting thread returns the exit status of the detached process when it
terminates, so you can use Thread#join
to know the result. If
specified pid is not a valid child process ID, the thread returns
nil
immediately.
The waiting thread has pid
method which returns the pid.
In this first example, we don't reap the first child process, so it appears as a zombie in the process status display.
p1 = fork { sleep 0.1 } p2 = fork { sleep 0.2 } Process.waitpid(p2) sleep 2 system("ps -ho pid,state -p #{p1}")
produces:
27389 Z
In the next example, Process::detach
is used to reap the child
automatically.
p1 = fork { sleep 0.1 } p2 = fork { sleep 0.2 } Process.detach(p1) Process.waitpid(p2) sleep 2 system("ps -ho pid,state -p #{p1}")
(produces no output)
Please login to continue.