The simplest solution that pops into my mind is a piped open. I haven't tried this on windows but it doesn't do anything fancy:
#!/usr/bin/env perl use warnings; use strict; my %cmds; my ($count, $limit, $actmax) = (0, 10, 2); my ($cmdline) = 'sleep 1; echo BOOM'; # I think this command will work in Windows but not sure... sub spawncmd { my ($cmd) = @_; my $pid = open(my $of, '-|', $cmd) or die "open: $!"; ++$count; $cmds{$pid} = $of; warn "Spawned $pid"; return $pid; } sub cleancmd { my ($pid) = @_; die "error: unknown cmd pid: $pid" unless(exists $cmds{$pid}); my $of = delete $cmds{$pid}; print "$pid: $_" while(<$of>); close($of); } spawncmd($cmdline) for(1 .. $actmax); while(keys(%cmds) > 0){ my $pid = waitpid(-1, 0); die sprintf("error: pid $pid had exit code %d", $? >> 8) if($? != +0); cleancmd($pid); spawncmd($cmdline) if($count < $limit); }

This simplifies things by blocking until one of the running commands exits, then reading the command's output all at once before closing the pipe. Standard output and error streams are read together and not separated with a piped open. You didn't specify whether you wanted them together or separate. Parallel processing seems unnecessary in this situation but maybe you have performance requirements you didn't mention.


In reply to Re: capture stdout and stderr from external command by juster
in thread capture stdout and stderr from external command by pankajadvani

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.