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!
|
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link or
or How to display code and escape characters
are good places to start.
|
