Seems we all agree. Strange ... ;-)
I didn't exactly expect that to be a controversial
node. The problem is, I keep running into people who
just don't think about logging program status, or
error conditions, or emitting any sort of status info
at all... those are the people I wrote the node
for.
On the subject of notification: cron(8) will
mail any output to you (well, to $MAILTO) after
each cron job. I imagine other similar facilities exist
elsewhere. Provided you don't get mail from your crons
on a regular basis ("Hey! I completed successfully!
Isn't that great?"), mail from cron(8) is an
effective error-reporting facility; you don't have to wait
until an error-checking/log polishing script runs at some
time in the future, you know right away when the job
finishes. (Or at least the next time you check your mail.)
--
|
F
o
x
t
r
o
t
U
n
i
f
o
r
m
|
Found a typo in this node? /msg me
The hell with paco, vote for Erudil!
|
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, 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, 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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
