You while loop will terminate when you've reached EOF on the pipe or there was an error. In the first case $bytes will be 0 and the second it'll be undef. To get the exit status of the child, you don't need to install a SIGCHLD handler. Just waitpid for the child process to terminate and check $?. So, here's one way to get the status w/o using SIGCHLD:
use POSIX ":sys_wait_h"; my $pid = open(INPIPE, "$reader_prog $options |") or die "open failed: + $!"; while ($bytes = read(INPIPE, $bugger, 32768)) { print $buffer; } if (!defined($bytes)) { print "read error: $!\n"; } my $kid = waitpid($pid, WNOHANG); unless ($kid == $pid) { print "child process $pid is still running\n"; print "trying close\n"; close(INPIPE); print "child status is $?\n"; } else { print "child process $pid reaped, status is: $?\n"; }
Notes:

In reply to Re: Children and return codes by pc88mxer
in thread Children and return codes by bot403

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.