From owner-freebsd-questions Wed Aug 16 16:41:40 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wilsonandhorton.co.nz (fw2.wilsonandhorton.co.nz [203.99.66.4]) by hub.freebsd.org (Postfix) with ESMTP id 1C2AE37BEB1 for ; Wed, 16 Aug 2000 16:41:20 -0700 (PDT) (envelope-from jonc@itouch.co.nz) Received: (from jonc@localhost) by wilsonandhorton.co.nz (8.9.3/8.9.3) id LAA07517; Thu, 17 Aug 2000 11:40:42 +1200 (NZST) (envelope-from jonc) Date: Thu, 17 Aug 2000 11:40:42 +1200 From: Jonathan Chen To: Nathan Vidican Cc: questions@FreeBSD.ORG Subject: Re: /etc/crontab not work? Message-ID: <20000817114042.C6387@jonc.ntdns.wilsonandhorton.co.n> References: <399A89CC.AA704AD6@wmptl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <399A89CC.AA704AD6@wmptl.com>; from webmaster@wmptl.com on Wed, Aug 16, 2000 at 08:32:12AM -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 16, 2000 at 08:32:12AM -0400, Nathan Vidican wrote: > I have two cron jobs which won't seem to run. If I run the exact same > commands from a shell script, then everything goes well. There are no > errors reported, nothing get's logged, yet nothing gets done either. The > two entries in question are as follows: > > # run Perl script which backs up our databases > # permissions set to 755, runs if user types: /etc/database-backup > # must be run as root, should run nightly at or around 8:00pm > 10 20 * * * root /etc/database-backup > 2>&1 | sendmail garbage You could check /var/logs/cron for further details; but my guess is that you need to put in an absolute pathname for the stuff in /etc/database-backup or path-out sendmail ie /usr/sbin/sendmail. Cheers. -- Jonathan Chen ---------------------------------------------------------------------- "Opportunity does not knock, it presents itself when you beat down the door" - W.E. Channing To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message