Quote:
Originally Posted by
mrm5102
Was the "Cron Problem Number One" page just saying don't use relative paths, use absolute? If that's the case then I'm ok there.
Actually this is a small part of it. The basic problem is: a scirpt started from commandline inherits the environment of the login shell, but a script started from cron inherits the environment of "init", which is next to empty. Guess what happens to heirs of poor processes? Sometimes they go broke, so to say. ;-))
This usually lands here in the form of: "my script worked perfectly from commandline, then i put it in a crontab and since then i doesn't work any more". We have these threads about once a week, which is why i started to call this "Cron Problem Number One". As you relate that your script works this seems not to be the case, but that was not clear from the start so i thought i'd mention it to put it on your checklist.
Regarding the suggested redirections: you just need to have some error condition and some command will write something to
stdout. I would redirect
any job in cron in the way i mentioned, just to be sure.
I hope this helps.
bakunin