AFAIR, system returns a combination of the actual return code and any signal that caused the call to die (as returned by wait) where the return code is the higher and the signal is the lower 8 bits of the 16 bit status return value.

Hence typical error detection avoids the process control signal data by shifting it out of the way before testing the return status - along the lines of... 

my $ret = system "args";
die "system($args) failed - status code: $ret" if $ret << 8;

[download]

HTH,

Update Thanx to pc88mer for noticing I got the wrong shift - should've read $ret >> 8 ... doh!!!

At last, a user level that overstates my experience :-))

In reply to Re: System call constantly dying by Bloodnok
in thread System call constantly dying by gokuraku

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.