Re^2: fixed set of forked processes

no data. not even failure or success, child capable of handling its own results. But the parent does need to know how many children are left running and update to OP: I also would prefer to avoid spawning a unix grep of unix ps to count subprocesses - that is also an unwanted overhead.

One world, one people

Comment on Re^2: fixed set of forked processes

Replies are listed 'Best First'.
Re^3: fixed set of forked processes by salva (Canon) on Dec 02, 2010 at 18:55 UTC
Then use Parallel::ForkManager or Proc::Queue.	[reply]
Re^4: fixed set of forked processes by tomfahle (Priest) on Dec 03, 2010 at 05:01 UTC
Have a look at Parallel::Iterator - Simple parallel execution, too. The workers option sets the number of concurrent processes to launch. `my $max_forks = 42; my $options = { workers => $max_forks, }; iterate( $options , $worker, $iterator );` [download]	[reply] [d/l]
Re^3: fixed set of forked processes by pileofrogs (Priest) on Dec 02, 2010 at 21:45 UTC
Your parent process will know the PID of each child process, so you can `kill 0, $pid` to see if it's running. Not sure what the performance implications are. Since you were mentioning ps & grep, I thought I'd mention this simple alternative. If all you want is to know if children are alive or dead, you might want to look into $SIG{CHLD} which tells you when kids die. That's in perlipc too. --Pileofrogs	[reply] [d/l]


XP is just a number
	PerlMonks