From owner-freebsd-questions@FreeBSD.ORG Thu Jun 14 00:16:19 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 B60A7106564A for ; Thu, 14 Jun 2012 00:16:19 +0000 (UTC) (envelope-from racerx@makeworld.com) Received: from omr12.networksolutionsemail.com (omr12.networksolutionsemail.com [205.178.146.62]) by mx1.freebsd.org (Postfix) with ESMTP id 704AC8FC15 for ; Thu, 14 Jun 2012 00:16:19 +0000 (UTC) Received: from cm-omr8 (mail.networksolutionsemail.com [205.178.146.50]) by omr12.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q5E0GDAA018963 for ; Wed, 13 Jun 2012 20:16:13 -0400 Authentication-Results: cm-omr8 smtp.user=racerx@makeworld.com; auth=pass (CRAM-MD5) X-Authenticated-UID: racerx@makeworld.com Received: from [50.44.138.106] ([50.44.138.106:19086] helo=[192.168.222.21]) by cm-omr8 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 1F/30-09498-C4D29DF4; Wed, 13 Jun 2012 20:16:13 -0400 Message-ID: <4FD92D52.50603@makeworld.com> Date: Wed, 13 Jun 2012 19:16:18 -0500 From: Chris User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <201206120506.q5C56L2H026673@mail.r-bonomi.com> <20120612190629.6a45cb11.freebsd@edvax.de> In-Reply-To: X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: Thu, 14 Jun 2012 00:16:19 -0000 On 6/13/2012 6:23 PM, Walter Hurry wrote: > 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 ... Damned those full path names. -- Keep well, Chris <><