It's the pipe. The exit value of something you pass to a shell, if it's a piped sequence, is the exit value of the last command:
$ cat nosuchfile | wc -l cat: nosuchfile: No such file or directory $ echo $? 0 $ cat nosuchfile cat: nosuchfile: No such file or directory $ echo $? 1
Some unix shells have workarounds for this, like the PIPESTATUS environment variable, or "set -o pipefail" in bash. Also, IPC::Run provides a built-in mechanism to pipe shell commands together and get the return value of all of them. Personally, I just avoid spawning shell commands with pipes, since it's usually the output of the first command that's interesting, and the function of the second command is almost always easily done within perl (sort, grep, tail, wc, etc).

In reply to Re: IPC::System::Simple: Why isn't my exception caught? by kschwab
in thread IPC::System::Simple: Why isn't my exception caught? by karlgoethebier

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.