Hi, On 2012-01-10 14:57, Ian Jackson wrote: > I have just been bitten by #625491. I looked in the logs, but there > was no trace of why my crontab files were not being executed. > > When it ignores a file because of the permissions cron should log a > warning with a reasonably high severity.
This should already be the case: root@home:/etc/cron.d# touch invalid; chmod 664 invalid root@home: tail -f -n 0 /var/log/cron.log (I have log facility "cron" redirected to a separate file -- by default, it should land in /var/log/syslog, I believe) The next time cron wakes up, I get: Jan 10 22:33:01 pequod /usr/sbin/cron[26690]: (*system*invalid) WRONG INODE INFO (/etc/cron.d/invalid) So the message is there, although not at helpful in -116. This has been improved in -117. Also fixed in -117 is the fact that earlier versions of cron could not recover from mode or syntax errors in /etc/cron.d -- a full restart was required. Could I trouble you to check again, considering the above? Regards, Christian
signature.asc
Description: OpenPGP digital signature
