You should also check for the exit status of the command when using pipe to invoke external commands.

open will fail

  • if it was not able to fork a process
  • the command was not found.
If there was any error in execting the command, it can be checked by closing the pipe and checking for the return value.

The sequence will be 

 
# opne the pipe, check if fork passed
open PIPE, "|$prog" or die $!; 
# do something with the command like
print PIPE @files;
# check if the command completed successfully
close PIPE or die "Command failed : $! || $?";

[download]

Hope this helps

-T

In reply to Re: Re: Unix command line by thens
in thread Unix command line by Anonymous Monk

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.