AM,

This is really not a perl problem but a cron issue. If you man crontab you may see: 

After cron runs commands according to the contents of your crontab 
file, it mails you the output from standard output and standard 
error for these commands, unless you redirect standard output
or standard error.

[download]

so you need to ensure you do not print any messages to either STDERR or STDOUT. A lot of devs will take a different tact than the one you have. You could set up your script to only print the msg and not e-mail you (and not do anything but exit if nothing new). Then let the cron subsytem mail you the results.

-derby

In reply to Re: Getting Perl to Die Gracefully by derby
in thread Getting Perl to Die Gracefully 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.