One way I've started using (thanks Dave B for the idea), is to get your process to log its pid when it starts (into a file or database table) and then remove that entry when it closes.

A little script starts every 10 minutes (either via cron or via a sleep command) and looks in the file/database for all the running processes. It then looks for those pids on the system using 'kill 0' tests. If it finds a pid in the list which isn't running it knows the process crashed.

For your purposes you may want this check script to run from cron so that it will reliably start every 'n' minutes.

The idea can be extended to support many jobs which you want to watch for failure. Hope this idea helps.

In reply to Re: Process Reliablity by barndoor
in thread Process Reliablity 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.