++ to the parent message.
To this point, cron's default behavior is to email all output to the user whose crontab invoked the process. Often times, the crontab output is redirected somewhere else , /dev/null being a popular choice, or other useful log file.
I tend to have my cron processes email success emails to one address, and failure to another address.
Good sysadmin's hook their processes into their favorite monitoring tools, TMTOWTDI.
Nothing is too wonderful to be true
-- Michael Faraday
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.