Date: Tue, 31 Oct 2006 12:28:51 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Martin McCormick <martin@dc.cis.okstate.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Trouble-shooting Cron Problems FreeBSD5.4 Message-ID: <20061031182850.GD3839@dan.emsphone.com> In-Reply-To: <200610311808.k9VI8Zgb031668@dc.cis.okstate.edu> References: <200610311808.k9VI8Zgb031668@dc.cis.okstate.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Oct 31), Martin McCormick said: > After building a new FreeBSD5.4 system, I have done > something bad to it. > > When cron runs jobs in /etc/crontab as operator, it seems > as if that 6TH field in /etc/crontab is being interpreted as a > command rather than the user ID it is supposed to run under. I > keep getting messages like: The "operator" user has no access to /etc/crontab. You have probably copied entries from the system crontab (i.e. /etc/crontab) into a user's crontab. The system crontab has the extra "user" column, where user crontabs don't (since they always run as the user). > From: operator@system.domainname (Cron Daemon) > Subject: Cron <operator@system> root newsyslog operator won't be able to run newsyslog anyway, since it can't write to /var/log and can't send signals to syslogd (which runs as root). You'll probably want to move those lines back to the system crontab. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061031182850.GD3839>