On Tue, Oct 03, 2006 at 02:51:51PM -0500, Damian Wiest wrote:
| Do whatever you like. I'm simply stating my preference and providing
| an alternative setup for people to consider. I don't find receiving
| 200+ messages a day from cron jobs running on the network with identical
| subject lines to be a particularly good setup. In this case, having
| cron mail me the results of the job is not "exactly what I want" as you
| seem to believe.
|
| If you can come up with a better scheme for managing emailed output from
| hundreds of jobs running on hundreds of machines, then please share.
| As it stands, you're merely trolling.
My cronjobs do not output anything when stuff Just Works (tm). When
something goes wrong, they will give output which will be sent to the
admin (me). As I usually don't receive any output from my cronjobs,
any cron mail I get indicates badness (except for the
daily/weekly/monthly crons that get installed by default). After
receiving such a mail, I will go in and fix the issue and the mails
stop. I don't need my backup cron to tell me that everything went
fine. That should be status quo.
This default behaviour of cron works pretty well for me, actually. If
I want succes-data accumulated over time, I'll make sure to do
adequate logging or send that particular data somewhere by other means
than the default cron mail facility.
Paul 'WEiRD' de Weerd
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
[demime 1.01d removed an attachment of type application/pgp-signature]
