How to recognize which child process has just ended?

[Lukasz Muziol]

Hi!

The piece of software I'm working on now needs to fork child processes
and execute different programs (which terminate themselves). Also, some
child processes need to be killed/stopped/resumed and action needs to be
taken when a child is terminated. When the parent receives & traps the
SIGCLD signal, how does it know which child it is regarding and whether
it has been ended, terminated, stopped or resumed?

In brief, I need the information, which in C signal handling is
accessible via the siginfo_t structure.

Thanks.

 

[Francis Cianfrocca]

Hi!

The piece of software I'm working on now needs to fork child processes
and execute different programs (which terminate themselves). Also, some
child processes need to be killed/stopped/resumed and action needs to be
taken when a child is terminated. When the parent receives & traps the
SIGCLD signal, how does it know which child it is regarding and whether
it has been ended, terminated, stopped or resumed?

In brief, I need the information, which in C signal handling is
accessible via the siginfo_t structure.

Thanks.

Look at Process#wait2 and Process#waitpid2.

 

[ara.t.howard]

Look at Process#wait2 and Process#waitpid2.

i don't think that's sufficient - one would still need a sig handler,
something along the lines of:


harp:~ > cat a.rb
require 'thread'

q = Queue.new

trap('SIGCHLD'){ q.push :go }

reaper = Thread.new do
Thread.abort_on_exception = true

loop do
q.pop
pid, status = Process.wait2
p [pid, status]
end
end


fork{ exit 42 }
sleep 1

fork{ exit 2 }

puts '...'
sleep


harp:~ > ruby a.rb
[26939, #<Process::Status: pid=26939,exited(42)>]
[26940, #<Process::Status: pid=26940,exited(2)>]
...


regards.

-a

 

[Francis Cianfrocca]

i don't think that's sufficient - one would still need a sig handler,
something along the lines of:

That's a surprise, what made you think so? Is that true on Windows,
perhaps? On Unix no sig handler is needed. SIGCHLD is ignored by
default. The following works:

#----------------------

fork {exit 42}
fork {exit 2}

Process.wait2
Process.wait2

#----------------------

You can also call #wait and its variants with the flag Process::WNOHANG
if you want to poll. Use a SIGCHLD handler if you need to know instantly
when a child process finishes, but as always observe the standard
guidelines for coding signal handlers.

 

[ara.t.howard]

Use a SIGCHLD handler if you need to know instantly
when a child process finishes, but as always observe the standard
guidelines for coding signal handlers.

sorry i wasn't more explicit - it's this that i interpreted the OP had wanted
since he asked to know __when__ the child exited not to do something whenever
it happened to. i may have been mistaken in my interpretation though...

in any case we are in total agreement.

-a

 

[Lukasz Muziol]

Thank you both.

As a matter of fact I do need to use a signal handler (the application
has an ncurses interface, so most of the time it's locked on getch calls
and action needs to be taken on child death), but the answer to my
problem is indeed the Process#wait2 method, which I somehow managed to
overlook.