On Monday 10 May 2010 11:05:52 martin f krafft wrote:
> This is a good fix, but I just wonder why this suddenly happens.
> The cronjob has been in place for years, and I have never seen such
> an e-mail.
It seems that cron 3.0pl1-110 started reporting cron jobs exiting with non-
zero status. See #
also sprach GSR [2010.05.09.0601 +0200]:
> I got the same email. But I think I understand why it does that and
> have a fix so it stops causing false alarms. It happens because the
> cron command tries to run once per month, but only the first sunday
> should checks be performed. So the second tes
Package: mdadm
Version: 3.1.1-1
Severity: normal
Tags: patch
Hi:
I got the same email. But I think I understand why it does that and
have a fix so it stops causing false alarms. It happens because the
cron command tries to run once per month, but only the first sunday
should checks be performed.
Package: mdadm
Version: 3.1.1-1
Severity: normal
When running cronjob, I get an error about checkarray:
Cron [ -x /usr/share/mdadm/checkarray ] && [ $(date +%d)
-le 7 ] && /usr/share/mdadm/checkarray --cron --all --quiet (failed)
command failed with exit status 1
When started from CLI, I get
4 matches
Mail list logo
