From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 13:41:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EB7E16A4CE for ; Thu, 5 Feb 2004 13:41:24 -0800 (PST) Received: from internet.potentialtech.com (h-66-167-251-6.PHLAPAFG.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D8D343D54 for ; Thu, 5 Feb 2004 13:41:19 -0800 (PST) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (pa-plum1c-102.pit.adelphia.net [24.53.179.102]) by internet.potentialtech.com (Postfix) with ESMTP id 8AA2669A4B; Thu, 5 Feb 2004 16:41:16 -0500 (EST) Message-ID: <4022B879.7030601@potentialtech.com> Date: Thu, 05 Feb 2004 16:41:13 -0500 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031005 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Jensen References: <20040205213711.5977660CD@bart.motd.dk> In-Reply-To: <20040205213711.5977660CD@bart.motd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Problems with cron after upgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2004 21:41:24 -0000 Tom Jensen wrote: > Hi, > > After I upgraded my 5.2-Current this morning to latest source I get error > mails from cron containing info like this > > Cron root /usr/libexec/atrun > root: not found > > and > > Cron operator /usr/libexec/save-entropy > operator: not found > > etc. > > Anybody seen this before?? Yes. You somehow got the system crontab to overwrite root's crontab. You probably want to just remove root's crontab and use the system crontab. Read the docs concerning cron carefully for the official explanation, but the quick explanation is: the system crontab has an extra field that specifies the user to run the task as, user crontabs always run the task as they user they were created by. root's crontab is no different than any other user's crontab. Anyway, the field that specifies the user in the system crontab is being interpreted as the command to run in the system crontab, thus the error message. Exactly how you got these two mixed up is something I won't guess at, but it seems to be a fairly common mistake. A search of the archives would have yielded the answer. -- Bill Moran Potential Technologies http://www.potentialtech.com