Date: Wed, 13 Jun 2012 19:16:18 -0500 From: Chris <racerx@makeworld.com> To: freebsd-questions@freebsd.org Subject: Re: Newbie question: Why aren't my cron jobs running? Message-ID: <4FD92D52.50603@makeworld.com> In-Reply-To: <jrb7ck$fut$1@dough.gmane.org> References: <201206120506.q5C56L2H026673@mail.r-bonomi.com> <op.wfsk2or734t2sn@tech304> <20120612190629.6a45cb11.freebsd@edvax.de> <CAPW8bZ1fFB8S0=kRpJ=X7w-Da=W4hjuXFHHTuZMc_Ac5FyTs3Q@mail.gmail.com> <jrb7ck$fut$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <><
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FD92D52.50603>