One of the things that I have is a step to capture the actual error messages that might go to STDERR. I try to capture all the output of a program into a logfile. I use an END block to determine whether the program exits cleanly or if its generated an error. Different exits determine differnt behaviors. For instance, when the program dies, it sends out an alert to a pager and makes a copy of the log so that I (or someone else) can look at the errored log and see what blew up (in case the actual log gets overwritten before we can get dialed in). You might look at using $SIG {__DIE__}. Just my own 2 cents though :-)

"Ex libris un peut de tout"

In reply to Re: perl script as a running process by nimdokk
in thread perl script as a running process by drfrog

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.