As written your delay is in the child fork. Instead you need to delay in the parent fork:

#!/usr/software/bin/perl5.8.8 -w

use strict;
use warnings;
use Cwd qw(abs_path);
use Parallel::ForkManager;

my $pm = new Parallel::ForkManager(8);
my $tasks = 3;

$pm->run_on_finish(
    sub {
        my ($pid, $exit_code) = @_;
        my $output = "$pid has finished with exit code $exit_code.\n";
        print $output;
    }
    );

for my $task (1 .. $tasks) {
    if ($pm->start($task)) {
        sleep 120 if $task != $tasks;
        next;
    }

    # This is the forked process
    my $time = time;
    print "$task\n";
    print "$time\n";
    $pm->finish();
}

$pm->wait_all_children;

[download]

Note that I haven't tested the code.

True laziness is hard work

In reply to Re: How to sleep before the next fork kicks off? by GrandFather
in thread How to sleep before the next fork kicks off? by dr.jekyllandme

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.