From owner-freebsd-questions@FreeBSD.ORG Wed Jun 13 23:23:22 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 296C6106566B for ; Wed, 13 Jun 2012 23:23:22 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id D4DFB8FC0A for ; Wed, 13 Jun 2012 23:23:21 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SewuE-0004ND-Qw for freebsd-questions@freebsd.org; Thu, 14 Jun 2012 01:23:18 +0200 Received: from cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com ([86.21.186.149]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jun 2012 01:23:18 +0200 Received: from walterhurry by cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jun 2012 01:23:18 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Walter Hurry Date: Wed, 13 Jun 2012 23:23:00 +0000 (UTC) Lines: 32 Message-ID: References: <201206120506.q5C56L2H026673@mail.r-bonomi.com> <20120612190629.6a45cb11.freebsd@edvax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 30dc37b master) Subject: Re: Newbie question: Why aren't my cron jobs running? 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: Wed, 13 Jun 2012 23:23:22 -0000 On Tue, 12 Jun 2012 12:21:31 -0500, Dan Lists wrote: > The syntax of his crontab file is correct. Vixie cron does care about > leading spaces, tabs, extra spaces, or leading zeros. Earlier versions > of cron are much pickier about the crontab file. The cron logs show > that it is starting his jobs at the correct times. > > It is far more likely that there is a problem with the scripts. A very > common cause of problems with scripts run from cron is that they do not > inherit your environment. Do the scripts run from the command line? > If the do, then the problem is most likely something in your environment > that the scripts need. I'm a complete idiot, and I feel embarrassed. Everything was fine, except that I had missed out '/bin' in the paths of the jobs. I had: /home/walterh/exports.sh /home/walterh/backup_etc.sh /home/walterh/systemcheck.sh /home/walterh/backup_bsd.sh which should of course have been: /home/walterh/bin/exports.sh /home/walterh/bin/backup_etc.sh /home/walterh/bin/systemcheck.sh /home/walterh/bin/backup_bsd.sh What a stupid mistake! Thanks for all the replies, but I must say sorry for wasting your time. Sorry! WH