From owner-freebsd-questions@FreeBSD.ORG Mon Dec 20 14:46:00 2004 Return-Path: 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 6139516A4CE for ; Mon, 20 Dec 2004 14:46:00 +0000 (GMT) Received: from fusion.vilot.net (vilot.com [64.246.32.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1216B43D49 for ; Mon, 20 Dec 2004 14:46:00 +0000 (GMT) (envelope-from tom@fusion.vilot.net) Received: from fusion.vilot.net (localhost.ev1servers.net [127.0.0.1]) by fusion.vilot.net (8.13.1/8.12.9) with ESMTP id iBKEhGUO018127; Mon, 20 Dec 2004 08:43:16 -0600 (CST) (envelope-from tom@fusion.vilot.net) Received: (from tom@localhost) by fusion.vilot.net (8.13.1/8.12.9/Submit) id iBKEhGaD018126; Mon, 20 Dec 2004 08:43:16 -0600 (CST) (envelope-from tom) Date: Mon, 20 Dec 2004 08:43:16 -0600 From: Tom Vilot To: Andy Clements Message-ID: <20041220144316.GA18006@vilot.com> References: <41BF2F0A.6020203@candhsoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41BF2F0A.6020203@candhsoftware.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org Subject: Re: cron not running job X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 14:46:00 -0000 > I'm having problems getting my freshly update FreeBSD 5.3 system to run > my cron jobs. Logged in as root, I enter the job in root's crontab with > the following command > > crontab -e > > I enter the job in the following format: > > 05 10 * * * /root/cronjobs/cvs-sup.sh > > The script has the following permissions: > > -rwxr-xr-x 1 root wheel 255 Dec 13 10:39 cvs-sup.sh > > I can run the script as root with no errors. I look in the > /var/log/cron log and I don't see any attempt by cron to run the job. > There is no error either. There are entries for the edit of the > crontab: This drove me batty for a while. You should see some emails to root regarding this. Typically, it's a path issue. In your cvs-sup.sh use the full path to the binaries you are trying to execute. Like this: /usr/local/bin/cvsup /root/ports-supfile > /tmp/ports-log 2>&1 /usr/local/sbin/portsdb -Uu Also, you can use /etc/periodic/daily rather than using cron directly.