"Three things ye must know about the wisewoman..." Oh wait, wrong topic.
Two things ye must know about the cron job...
- One of the best ways to debug a cron job is to put in lines like this:
Code:
echo "At start of myscript" >>/tmp/myscript.debug.$$.log
Put somthing like this near the beginning, another at the end, ... You get the picture. Don't forget to remove or comment them out when you're done debugging. Even more informative:
Code:
/usr/bin/env >>/tmp/myscript.debug.$$.log
- cron jobs run in stripped envionment, among other things that means that you don't have a full path, and shouldn't assume any. As a result you should always test a script intended for a cron job like this:
Code:
env -i myscript.sh
This will let you spot any unwarranted assumptions about your environment.
So given this, the bug in your script should be obvious, replacing:
Code:
su mythtv -c "mythfilldatabase --quiet"
with this:
Code:
/bin/su mythtv -c "/usr/bin/mythfilldatabase --quiet"
should solve your problem.