Silly example, but might help. 
#! perl -slw
use POSIX qw(:errno_h :sys_wait_h);

use constant {
  RET_SUCCESS => 1,
  RET_FAILURE => 0,
};

sub check_process_signal {
  my $sig = shift;
  if ( WIFEXITED($sig) ) {
    print q{process normal exit};
    return RET_SUCCESS;
  } elsif ( WIFSIGNALED($sig) ) {
    print q{process terminated because of signal};
    return RET_FAILURE;
  }  elsif ( WIFSTOPPED($sig) ) {
    print q{process is stopped};
    return RET_FAILURE;
  }
  return RET_SUCCESS;
}

my $pid = #run your command however....

waitpid( $pid, 0 );
if ( check_process_signal( $? ) ) {
  ## success...
} else {
  ## failure ...
}

[download]

Coded on the fly sorry if there are any errors.

--Poet

In reply to Re^4: Background process by DeadPoet
in thread Background process by tart

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.