Excerpts from Christian Kastner's message of Wed May 19 10:10:25 -0700 2010:
I just re-read #443615. I understand the wish for such a feature, and
have added it to my ideas list (among #373152 et al). Such a feature
could be added in squeeze+1, via a --strict flag or similar, but I won't
On 05/19/2010 12:03 AM, Justin T Pryzby wrote:
clone 581612 -1
reassign -1 php4
retitle -1 php4: update test avoiding nonzero exit status when
removed-but-not-purged
thanks
If it is desired behavior that cron now sends out email if the job
exit's with
status 1, it is strange that I now
You want cron to allow a job to fail silently? Although avoiding
noise from some existing package cron.d jobs is additional work,
having an assertive cron helps people to catch otherwise-invisible
problems (Andrew Pimlott in #443615). Andrew? Perhaps you have a
specific, convincing scenario
On 05/19/2010 03:28 PM, Justin Pryzby wrote:
You want cron to allow a job to fail silently?
The question is not what I want to do, it's what can I /can/ do.
Although avoiding
noise from some existing package cron.d jobs is additional work,
having an assertive cron helps people to catch
I upgraded my machine today. After about a hour I had 22-25 mails nagging me
that my different cron jobs telling me the same:
command failed with exit status 1
The error came from the following cron jobs:
/etc/cron.d/dma:
*/5 * * * * root[ -x /usr/sbin/dma ] /usr/sbin/dma -q1
clone 581612 -1
reassign -1 php4
retitle -1 php4: update test avoiding nonzero exit status when
removed-but-not-purged
thanks
If it is desired behavior that cron now sends out email if the job exit's
with
status 1, it is strange that I now get a lot of mail from system cron jobs
Those
6 matches
Mail list logo
