[nycbug-talk] crontab woes

[Dan Langille]

On 19 Jul 2005 at 16:48, Kevin Reiter wrote:

> All,
> 
> I'm ready to pull my hair out on this one..
> 
> I have a crontab setup to run a small shell script every day at 1:15 am. 
>   The script writes to a log so I can follow the activity, but I've 
> noticed it's empty.  When I do some further checking to see if the 
> script did what it's supposed to do, I see that it didn't run at all.
> 
> Here's the crontab entry:
> 
> root at Vulcan# crontab -l
> # Run the script every night at 1:15 AM
> 15 1 * * * /root/scripts/myscript.sh
> 
> The script is in place, is executable, and runs just fine if I do 
> ./myscript.sh
> 
> cron is running:
> 
> root at Vulcan# ps wax | grep cron
>    154  ??  Ss     0:06.88 /usr/sbin/cron
> 
> root at Vulcan# uname -a
> FreeBSD Vulcan 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Sat Mar 13 10:13:57 
> EST 2004     root at Vulcan:/usr/obj/usr/src/sys/Vulcan  i386
> 
> Any ideas?  This is something so simple, yet very exhasperating.

Make sure you press ENTER at the end of the line.

Verify via /var/log/crontab that the job actually gets run.
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/