Moving the wait is not enough 

+------------------------+----------------------+
| Parent                 | Child                |
+------------------------+----------------------+
| - open3(...);          |                      |
| - <OUT>                | - ...                |   |
|   - Waits for child to | - print STDERR 1027; |   |
|     write to STDOUT or | - print STDERR 1028; |   |
|     for child to end.  | - print STDERR 1029; |   T
|                        | - print STDERR 1030; |   i
|                        | - print STDERR 1031; |   m
|                        |   - Pipe full.       |   e
|                        |     Waits for parent |   |
|                        |     to empty it.     |   |
|                        |                      |   v
| Still waiting...       | Still waiting...     |
+------------------------+----------------------+

[download]

With my snippet below, you don't have to store the stuff in memory. You can do whatever you want to with it when you read it it. For example, the following prints it out a line at a time, prefixed with the handle name: 

my %lookup = (
   \*OUT => [ \*OUT, 'STDOUT', '' ],
   \*ERR => [ \*ERR, 'STDERR', '' ],
);

MAIN_LOOP:
for (;;) {
   my @r = $r_sel->can_read();

   foreach my $fh (@r) {
      last MAIN_LOOP if eof($fh);

      my $buf_ptr = $lookup{$fh}[2];
      1 while read($fh, $$buf_ptr, $BLOCK_SIZE, length($$buf_ptr));

      print("$lookup{$fh}[1]: $1")
         while $$buf_ptr =~ s/^(.*\n)//;
   }
}

foreach my $fh (keys %lookup) {
   print("$lookup{$fh}[1]: $lookup{$fh}[2]\n")
      if length $lookup{$fh}[2];
}

[download]

Alternatively, you could use IPC::Run. Instead of a scalar, you can pass the address of a callback to be called when text is received from the child. (Search for \&out.)

In reply to Re^3: Script hangs when called via IPC::Open3 by ikegami
in thread Script hangs when called via IPC::Open3 by jeffa

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.