Parallel-ForkManager
view release on metacpan or search on metacpan
README.mkdn view on Meta::CPAN
- identification of the process (if provided in the "start" method)
```
- run\_on\_wait $code, \[$period\]
You can define a subroutine which is called when the child process needs to wait
for the startup. If $period is not defined, then one call is done per
child. If $period is defined, then $code is called periodically and the
module waits for $period seconds between the two calls. Note, $period can be
fractional number also. The exact "$period seconds" is not guaranteed,
signals can shorten and the process scheduler can make it longer (on busy
systems).
The $code called in the "start" and the "wait\_all\_children" method also.
No parameters are passed to the $code on the call.
# BLOCKING CALLS
When it comes to waiting for child processes to terminate, `Parallel::ForkManager` is between
a fork and a hard place (if you excuse the terrible pun). The underlying Perl `waitpid` function
lib/Parallel/ForkManager.pm view on Meta::CPAN
- pid of the process which has been started
- identification of the process (if provided in the "start" method)
=item run_on_wait $code, [$period]
You can define a subroutine which is called when the child process needs to wait
for the startup. If $period is not defined, then one call is done per
child. If $period is defined, then $code is called periodically and the
module waits for $period seconds between the two calls. Note, $period can be
fractional number also. The exact "$period seconds" is not guaranteed,
signals can shorten and the process scheduler can make it longer (on busy
systems).
The $code called in the "start" and the "wait_all_children" method also.
No parameters are passed to the $code on the call.
=back
=head1 BLOCKING CALLS
( run in 0.235 second using v1.01-cache-2.11-cpan-87723dcf8b7 )