Christian Kastner writes ("Re: Bug#655340: cron should log when it ignores a
crontab file"):
> 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.
Oh yes, so it is. It's just that it took cron 2 seconds to decide to
print the message:
Jan 10 10:29:50 chiark /usr/sbin/cron[3163]: (CRON) STARTUP (fork ok)
...
Jan 10 10:29:52 chiark /usr/sbin/cron[3163]: (*system*localconsolelive) WRONG
INODE INFO (/etc/cron.d/localconsolelive)
On my system 2 seconds is a long time and in this case there were
quite a few other lines in between and evidently I didn't wait 2
seconds personally.
So, yes, I think this bug can be closed, unless you think the delay is
worth a bug ?
Ian.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
