Re: how much beer do I need to get this patch applied?

On 6/20/07, Jo Rhett <jrhett@xxxxxxxxxx> wrote:
On Jun 20, 2007, at 10:40 AM, Kurt Buff wrote:

> On 6/20/07, Dan Rue <drue@xxxxxxxxxx> wrote:
>> If it's too broken to complain, then the behavior is the same with or
>> without this patch.
>
> Indeed, which is why this patch might not be such a good idea. In this
> case, absence of evidence is indeed evidence of absence, which is
> contrary to the general case.

You appear to be completely confused about what this change does.
All it does is TO ALLOW (not require) the OP to disable the spurious
and empty output from successful cron jobs.

If I get a message every day saying "No output", how do I know when a
failure has occurred? This patch changes nothing about that
behavior. Getting no message is equally useless in the situation
where no output was generated *AND* the result code is positive.

Currently, if you get no message from that box, *something* is broken.

The more likely is that the OP starts deleting the messages unread
each day and thus never sees an actual failure report.

Failure of imagination.

> Perhaps the OP needs a better way of dealing with the notifications
> than simply turning them off.

How do you suggest dealing with 1200-1800 messages which simply say
"no output" each day? The commands were successful, and the
processes had no output.

1. In that load level I won't notice one missing, so absence of the e-
mail is not useful.

2. In that load level I can't possibly read them all. So actual
reports of failure will be overlooked.

3. Actual errors *will* be reported, and *will be read* if I don't
have to delete thousands of non-errors.

Perhaps a separate mailbox dedicated to this task, with a script
(grep?) that parses the emails in that mailbox daily looking for
expected messages, noting and deleting them, with unsent messages
noted via an email and messages with unexpected content forwarded as
well?

Kurt
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Problems installing BitDefender on Windows ME
    ... I was only able to get it to run once in a compromised mode, although it did indeed locate a number of infected files which I was later able to delete manually. ... There are three error messages that are displayed in at least two failure modes. ... This failure occurs regardless of whether the program is started automatically or manually. ... A patch that's shown on the publisher's web site. ...
    (alt.comp.anti-virus)
  • Help me!
    ... I am a proper smoker, practically a career smoker, 40 a day. ... Went downstairs and drank a pint of Ribena, and while I was there slapped on my first patch. ... By now I've kicked off SilkQuit and it is tormenting me by highlighting my complete failure so far. ... Went through bin and found packet of Amber Leaf and went to hide behind shed for a roll-up. ...
    (alt.support.stop-smoking)
  • Re: Help me!
    ... Hope its OK for a Newbie to drone on about their failure. ... slapped on my first patch. ... Went to visit computer, subscribed to this group, and downloaded SilkQuit. ... for a roll-up. ...
    (alt.support.stop-smoking)
  • Re: rtc-cmos.c: Build fix
    ... It had a build failure with this config: ... stubs because it was removed with akpm's patch. ...
    (Linux-Kernel)
  • Re: Excessive Outgoing email
    ... "david smith" wrote in message ... We currently have 10000+ emails in our outgoing ... >>There is a Microsoft patch which covers this for SBS 2003 ...
    (microsoft.public.backoffice.smallbiz2000)