4 ms·
That's a lie. A mail is sent on failed jobs. Please don't use the lie word: it goes to intentionality. It's wrong, true: Cron has (for a very long time) been d
by ggm 7y ago
That's a lie. A mail is sent on failed jobs.
Please don't use the lie word: it goes to intentionality. It's wrong, true: Cron has (for a very long time) been designed to mail and log on failure.
The thing is that a huge number of deployments these days don't run functional mail send, and so the failure states go to /dev/null (in effect)
Also, cron can fail to run: Linux moved cron to a different execution state from BSD, which has also introduced (on linux) the interaction between cron and anacron. Changing the state of cron.d/ doesn't always register in cron, and cron won't always send mail if it doesn't know new things have to be run. The older crontab -e method reliably made cron re-read the state of the file.
(I think this predated Vixie cron, cron existed since time immemorial in UNIXEN. Vix improved things, but the underlying system behaviour was established before he coded in this space)
- scbrg 7y ago> Please don't use the lie word: it goes to intentionality. If someone built a whole product around it - and use it as their marketing pitch when it takes like 30 seconds of man-page reading to find out that it's wrong, I'd argue you have some fairly good reason to assume intentionality. (That said, yes, I agree that there are failure states in traditional cron that won't alert you with an email, so the service might of course be useful.)