Re: Monitoring Child Process

It would probably be better to keep your kid pids as keys in a hash, then delete them as they are reaped. You are currently printing all of the pids that were created on ctl-C.

Comment on Re: Monitoring Child Process

Replies are listed 'Best First'.
Re^2: Monitoring Child Process by Anonymous Monk on Oct 19, 2011 at 18:59 UTC
I'm not sure what you mean, but I incorporated your suggestion and it didn't solve the problem. When I run the script (without pressing ctrl-c), it will say something like this at the end... `Process 2555 exited. Process 2558 exited.` [download] The problem is that I know the script create processes 2556 and 2557 and the REAPER subroutine somehow did not catch it and in reality these children have exited already.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Monitoring Child Process
by Anonymous Monk on Oct 19, 2011 at 18:59 UTC

Process 2555 exited.
Process 2558 exited.
[download]

[reply]
[d/l]