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 otherwise-invisible > problems (Andrew Pimlott in #443615). Andrew? Perhaps you have a > specific, convincing scenario handy. I consider this a major change, not only for our cron but also from all other vixie-cron based implementations out there. It would be absolutely impossible to implement this change responsibly on such short notice (ie, for squeeze). As you said, this would probably cause issues for other packages. This means that I would have to conduct a MBF and give Maintainers time to fix this. And the impact on users would be even worse, NEWS entry or not (the fetchmail issue alone, with 6% popcon, would be bad enough). 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 promise it. For now, I suggest Andrew do the inverse of your suggestion and add || echo "FOO failed" to those entries for which a mail should be sent on non-zero exit. Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
