Re: [MAYBE SPAM] Re: Looking for HowTo instructions ...

2006-10-04 Thread Paul de Weerd
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]



Re: [MAYBE SPAM] Re: Looking for HowTo instructions ...

2006-10-03 Thread Damian Wiest
On Tue, Oct 03, 2006 at 03:06:20PM -0400, Adam wrote:
  Damian Wiest [EMAIL PROTECTED] wrote:
 
  On Mon, Oct 02, 2006 at 07:54:05PM -0400, Adam wrote:
   Damian Wiest [EMAIL PROTECTED] wrote:
   
Suppose your cron jobs don't emit output, which any good job shouldn't 
do.
   
   Huh?  If you want a task to run on a schedule, and then mail you the 
   results,
   then cron is exactly what you want.  Any good job does what its author
   wants it to.  If they want it to emit output, then having it be silent for
   no reason does not make it a good job.
   
   Adam
  
  The way I structure my jobs, no output is _ever_ mailed by the cron 
  daemon.  Instead, the job itself traps output and sends an appropriate 
  email message, with an appropriate subject to the appropriate user.
 
 Good for you.  But what Damian likes to do is not the definition of
 good.

It's my definition :)

  Like I said, if someone wants output mailed from cron, then
 making the job silent just because Damian thinks that's good is dumb.
 
 Adam

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.

-Damian



Re: [MAYBE SPAM] Re: Looking for HowTo instructions ...

2006-10-03 Thread Adam
Damian Wiest [EMAIL PROTECTED] 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.

I didn't say its exactly what you want, I said its exactly what the person
asking about periodic wants.  You are the one making blanket statements
about bad cron jobs without considering what is intended.

 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.

I don't need to come up with any such scheme, as I don't have any such
problem.  I simply said that cron is ideal for running a task and then
sending an email about it.  This is true wether you let cron send the
mail or if you do it yourself in the script.  I think you need to learn
what a troll is, or stop tossing it around like that.  You are not the
definition of good, and telling you as much is not trolling.

Adam