Good call. 
defined( my $pid = open(CMD, '-|') )
    or die("Can't fork: $!\n");

if ($pid == 0) {
    close(STDERR);
    open(STDERR, ">&STDOUT")
        or print "Unable to reopen STDOUT, errors may be lost: $!";
    exec('/bin/tar', 'czf', '/nonexistent/test.tar.gz', '.')
        or die("Unable to exec: $!")
}

local $/ = undef;
my $output .= <CMD>;

close(CMD);

if    ($? == -1) { die("Can't close pipe: $!\n"); }
elsif ($? & 127) { die("tar died from signal ", ($? & 127), "\n"); }
elsif ($? >> 8)  { die("tar exited with error ", ($? >> 8), "\n"); }

print $output;

[download]
tar died from signal 13

[download]

In reply to Re^2: Exit codes from forking children by ikegami
in thread Exit codes from forking children by DustinLundquist

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.