Perhaps I'm not fully understanding the question, but it seems like the solution you have, and the ones already given by pizza_milkshake, are overcomplicating things a bit. Here's how I'd code this thing:

use strict; use warnings; my @isolist = qw(one two three four five); # should contain ISO names while (my @workunit = splice @isolist, 0, 3) { my @pids; for (0 .. $#workunit) { push @pids, burncd($workunit[$_], $_); } waitpid $_, 0 for @pids; print "Work unit finished.\n"; if (@isolist) { # perhaps a prompt here to put in new blanks print "Starting next round...\n"; sleep 3; } } sub burncd { my ($isoname, $target) = @_; my $pid = fork; die "Cannot fork: $!" unless defined $pid; return $pid if $pid; print "Burning $isoname to cdrw$target\n"; # burn the cd. randomized sleep just for testing. sleep int rand(5) + 5; exit; }

In reply to Re: forking and ipc by revdiablo
in thread forking and ipc by hambo

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.