I use
Parallel::ForkManager for most of my forking these days.
it setup nice callbacks for Start/wait/finish of children
heres a snipit:
# when a childe spawns
$pm->run_on_start(
sub {
my ($pid,$ident)=@_;
log_report("Parent Starting Child $pid Sending to $ident");
});
# when a childe finishes
$pm->run_on_finish(
sub {
my ($pid, $exit_code, $ident, $error) = @_;
log_report( "Child at $pid completed on $ident with code:$exit
+_code");
});
# while we wait..
$pm->run_on_wait( sub{log_report( "Waiting for children ..." );} );
of course this is pretty simplistic :-) read the docs for more info. I imagine you caould build up some sort of execution chain ? for a task then independentl;y walk that chain. assuming you know that task X requires task A and B.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.