---- Original message ---- >Date: Wed, 4 Oct 2006 12:25:08 -0600 >From: "Chris Kuethe" <[EMAIL PROTECTED]> >Subject: Re: [most likely OT] Re: cron jobs >To: "Ben Calvert" <[EMAIL PROTECTED]> >Cc: "Paul de Weerd" <[EMAIL PROTECTED]>, [EMAIL PROTECTED], misc@openbsd.org > >On 10/4/06, Ben Calvert <[EMAIL PROTECTED]> wrote: >> I'm sorry to jump in here, but I'm really curious about how you tell the diference between the job never running and it Just Working (tm)? >> >> I don't know about you, but particularly in the case of backup i'm very interested in making sure it worked successfully. >> >> It strikes me that this 'no news is good news' policy creats a single point of failure (cron).
you're overlooking the more significant single point of failure, PEBKC. > >Cron provides you with a mechanism for running jobs on some regular >interval, and will helpfully pass along any output from your job via >email. That's it. > >It's up to you to think about what kind of notification you need. It's >UNIX' job to provide the tools, it's your job to provide the brains. >And keep your fingers away from the band-saw... > is my face red? just call me mr. butterfingers! >CK > >-- >GDB has a 'break' feature; why doesn't it have 'fix' too?
