It has for me. I misspelled something in a script and cron sent me an
email complaining about it.
On 01/03/15 09:50, Craig Skinner wrote:
Back in the memory of somewhere??? I worked,
failed cronjobs would mail their return code if not zero.
Something like: Cron Job false exited with return
+--
| On 2015-01-03 14:02:15, Matthew Weigel wrote:
|
No, the behavior he described is accurate: cron(8) sends email if a job
produced output, irrespective of its exit status.
Google is littered with people trying to
On Jan 03 15:50:36, skin...@britvault.co.uk wrote:
Back in the memory of somewhere??? I worked,
failed cronjobs would mail their return code if not zero.
Something like: Cron Job false exited with return code 1
I cannae mind if it was Solaris or Linux, or whatever they were using...
Can
On 01/03/15 15:50, Craig Skinner wrote:
Back in the memory of somewhere??? I worked,
failed cronjobs would mail their return code if not zero.
Something like: Cron Job false exited with return code 1
I cannae mind if it was Solaris or Linux, or whatever they were using...
Can OpenBSD's cron do
Back in the memory of somewhere??? I worked,
failed cronjobs would mail their return code if not zero.
Something like: Cron Job false exited with return code 1
I cannae mind if it was Solaris or Linux, or whatever they were using...
Can OpenBSD's cron do that too?
Here's some silent noisey
On 1/3/15 1:05 PM, Fred wrote:
man 5 crontab not man 1 crontab
:~)
No, the behavior he described is accurate: cron(8) sends email if a job
produced output, irrespective of its exit status.
Google is littered with people trying to figure out how to get cron(8)
to send email based on exit
6 matches
Mail list logo
