On 03/19/2012 09:16 AM, 郑文辉(Techlive Zheng) wrote:
Hi,I don't know whether this is a bug or something, but I can not
find
what caused this. I was suggested by someone to report to the
upstream, so here I am.
I am a Arch Linux User, and cronie is now Arch default cron daemon.
The following messages have spammed my errors.log and crond.log for a
few days, I don't know how to stop it.
Feb 6 04:00:01 vbox03 /usr/sbin/crond: (CRON) This directory or
file can't be watched (/etc/crontab): No such file or directory
Feb 6 04:00:01 vbox03 /usr/sbin/crond: (CRON) INFO (running
without inotify support)
Feb 6 04:00:01 vbox03 /usr/sbin/crond: (root) CAN'T OPEN
(/etc/crontab): No such file or directory
Feb 6 04:00:01 vbox03 /usr/sbin/crond: (*system*) RELOAD
(/etc/cron.d/0hourly)
Feb 6 04:01:01 vbox03 /usr/sbin/crond: (CRON) This directory or
file can't be watched (/etc/crontab): No such file or directory
Mar 17 12:21:34 vbox03 /usr/sbin/crond: (CRON) INFO (running with
inotify support)
Mar 17 23:10:39 vbox03 /usr/sbin/crond: (CRON) STARTUP (1.4.8)
Mar 17 23:10:39 vbox03 /usr/sbin/crond: (CRON) INFO (running with
inotify support)
Mar 17 23:10:39 vbox03 /usr/sbin/crond: (CRON) INFO (@reboot jobs
will be run at computer's startup.)
Mar 18 05:34:01 vbox03 /usr/sbin/crond: (root) CAN'T OPEN
(/etc/crontab): No such file or directory
Mar 18 05:52:01 vbox03 /usr/sbin/crond: (root) CAN'T OPEN
(/etc/crontab): No such file or directory
Mar 18 05:52:01 vbox03 /usr/sbin/crond: (*system*) RELOAD
(/etc/cron.d/ispcp)
Mar 18 06:30:55 vbox03 /usr/sbin/crond: (CRON) STARTUP (1.4.8)
Mar 18 06:30:56 vbox03 /usr/sbin/crond: (CRON) INFO (running with
inotify support)
Mar 18 06:30:56 vbox03 /usr/sbin/crond: (CRON) INFO (@reboot jobs
will be run at computer's startup.)
Mar 18 08:08:18 vbox03 /usr/sbin/crond: (CRON) STARTUP (1.4.8)
Mar 18 08:08:18 vbox03 /usr/sbin/crond: (CRON) INFO (running with
inotify support)
Mar 18 08:12:59 vbox03 /usr/sbin/crond: (CRON) STARTUP (1.4.8)
Mar 18 08:12:59 vbox03 /usr/sbin/crond: (CRON) INFO (running with
inotify support)
Mar 18 18:03:34 vbox03 /usr/sbin/crond: (CRON) STARTUP (1.4.8)
Mar 18 18:03:34 vbox03 /usr/sbin/crond: (CRON) INFO (running with
inotify support)
Mar 18 18:05:16 vbox03 /usr/sbin/crond: (CRON) STARTUP (1.4.8)
Mar 18 18:05:16 vbox03 /usr/sbin/crond: (CRON) INFO (running with
inotify support)
Mar 18 18:16:06 vbox03 /usr/sbin/crond: (CRON) STARTUP (1.4.8)
Mar 18 18:16:06 vbox03 /usr/sbin/crond: (CRON) INFO (running with
inotify support)
Mar 18 22:13:01 vbox03 /usr/sbin/crond: (root) CAN'T OPEN
(/etc/crontab): No such file or directory
Mar 18 22:13:01 vbox03 /usr/sbin/crond: (*system*) RELOAD
(/etc/cron.d/ispcp)
I thought cronie does not need /etc/crontab any more, but why it
complains about it in the log?
Here is the original disscussion in the Arch General Mailing List:
http://thread.gmane.org/gmane.linux.arch.general/39947
If you need any further details, please let me know, I will provide
anything that could help.
Hi,
on my computer is the warning printed out everytime I modify some
crontab. In my distribution (Fedora) is /etc/crontab still created, but
empty. Some users prefer to set up their daily jobs here.
If the warning wasn't printed, it might be a problem for people using
it. I guess I could add some tweak into Makefile, so distribution could
pick if they compile the support with or without /etc/crontab. I added
it into our trac to think about it more [1].
Regards,
Marcela
[1]
https://fedorahosted.org/cronie/ticket/10