As mentioned I would prefer not to use IPC::Run because IPC::Run is not installed on many of the old distributions supported by GNU Parallel, whereas open3 is. There is typically a reason why people do not upgrade the old systems, and it is therefore unlikely that IPC::Run will be installed.

The PID is currently the way I keep track of which process was started when, so when using --keep-order, I can make sure the output from the dead children is printed in the correct order. But with a bit of recoding this could probably be changed.

I had hoped wrapping open3 with more filedescriptors would be as easy as this meta-code for fd3: 

# Record fd3 for later use
open($orig_fd{3},">&=",3);
for $id (1..10) {
  open($child{$id,3},">",$tmpfile{$i});
  # make $child{$id,3} file descriptor 3 for me and all future childre
+n
  connect_filedescriptor(3,$child{$id,3});
  # start the child
  open3(...)
}

sub reaper {
  # When a child dies
  seek $child{$id,3},0,0;
  # Print the captured fd3 to the parent's original fd3
  print $orig_fd{3} <$child{$id,3}>;
  close $child{$id,3};
}

[download]
I know how to make most of the meta-code, but connect_filedescriptor I do not know how to make.

In reply to Re^2: open3 but for n file descriptors by tange
in thread open3 but for n file descriptors by tange

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.