From owner-freebsd-questions@FreeBSD.ORG Tue Oct 31 18:30:19 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1BD416A4A7 for ; Tue, 31 Oct 2006 18:30:19 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DCDC43ED6 for ; Tue, 31 Oct 2006 18:28:58 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.6/8.13.8) id k9VISpio022325; Tue, 31 Oct 2006 12:28:51 -0600 (CST) (envelope-from dan) Date: Tue, 31 Oct 2006 12:28:51 -0600 From: Dan Nelson To: Martin McCormick Message-ID: <20061031182850.GD3839@dan.emsphone.com> References: <200610311808.k9VI8Zgb031668@dc.cis.okstate.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200610311808.k9VI8Zgb031668@dc.cis.okstate.edu> X-OS: FreeBSD 6.2-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-questions@freebsd.org Subject: Re: Trouble-shooting Cron Problems FreeBSD5.4 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2006 18:30:20 -0000 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 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