I think a pid file in /var/run is the right approach, maybe because that's what we do. You can easily have the cron print to stdout that it is dying because it sees the pid file of an earlier process. That stdout goes to the email address of the cron owner who always (well usually) pays attention to such things.

It is also problematic if your script dies without logging or otherwise informing you. It's not always possible, but you should try hard to make autononmous scripts log and generate nasty grams when things go wrong (by trapping signals, evaling things that could die, etc).

Phil

In reply to Re: Cron Jobs That Run For Too Long by philcrow
in thread Cron Jobs That Run For Too Long by beppu

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.