in reply to Parallel::ForkManager and wait_all_children
fork+system+exit is wasteful. It creates a process whose entire purpose is to launch another process and wait for it to finish. Let's start by simplifying to fork+exec.
while (1) { for my $runCommand (@runArray) { $forkMgr->start($runCommand) and next; exec("/usr/localcw/opt/patrol/nagios/libexec/$runCommand") or die("exec: $!"); } $forkMgr->wait_all_children; sleep 10; }
Now, on to your problem. Your proposed solution of letting hung workers stay hung doesn't make much sense. You'll eventually end up with three hung workers. You gotta kill them if they become hung. Unless you have a better condition based on knowledge of the test programs, a process can be considered hung if it has been running more than some configured amount of time.
Since we can execute code in the process that will execute the test program, all we need to do is call alarm from that process.
use constant TIMEOUT => 60; while (1) { for my $runCommand (@runArray) { $forkMgr->start($runCommand) and next; alarm(TIMEOUT); exec("/usr/localcw/opt/patrol/nagios/libexec/$runCommand") or die("exec: $!"); } $forkMgr->wait_all_children; sleep 10; }
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Parallel::ForkManager and wait_all_children
by RichardK (Parson) on May 13, 2015 at 09:29 UTC | |
by afoken (Chancellor) on May 13, 2015 at 19:20 UTC | |
by ikegami (Patriarch) on May 13, 2015 at 21:38 UTC | |
by moritz (Cardinal) on May 13, 2015 at 13:17 UTC | |
by ikegami (Patriarch) on May 13, 2015 at 21:36 UTC | |
by rgren925 (Beadle) on May 13, 2015 at 22:13 UTC | |
by ikegami (Patriarch) on May 14, 2015 at 14:31 UTC |