Personally I hate using platform specific modules if I can avoid it. When you start with a nice portable language, it is worth a little effort to not lose portability.

The key to my approach is the IPC::Open3 module and the wait command. The module exports open3, which lets you launch a process with specified STDIN, STDOUT, and STDERR. The return of that is a process ID. Conversely wait will collect the return of a process you launched (the processes are called "children" and this is called "reaping the process" since it is the last step before the process can finish dying) returning the process ID and setting $? to its return code.

What I did is launched processes hooked directly to my output but supressing all input (because there is no easy way to sort out you being able to talk to 5 processes at once on one pipe) and kept track of what I launched. When I reaped them if there was a problem I would give a message based on what I had. My logic was complicated by the fact that I might have 200 jobs to launch, but don't want to run more than 5 at a time. However that is the idea.

See if you can't get that to work. If you do you will both have more portable code and will have learned a lot about process communication..both good things IMO. :-)

In reply to RE (tilly) 2 (explanation): Opening simultaneous scripts by tilly
in thread Opening simultaneous scripts by OzzyOsbourne

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.