Solaris

is the script woodget2 having executable permissions ?. Many times we people forget to give that.

Cron isnt at fault here, the script is. Have you remembered that cron does not read profiles and does not have any user environmental settings ?? Any script that runs should assume this and define any variabvles, home directories. Ive just had a similar problem with a DBA who wrote a few scripts and nothing worked. "Cron is broken" was his loud cry accross the room.

Well, turns out his script didnt set any variables or paths so commands werent found and the script never ran.

What I suggest you do is have a play, run the script in verbose mode :-

Code:

#!/bin/ksh -v or -x

,

Then re-direct the output of the file, within the script, to a file

Code:

exec 1>> /tmp/script-output.txt
exec 2>&1
exec 3>&1

or adjust the cron entry to redirect output from the script :-

Code:

0 * * *  * /path/to/script/script  >/tmp/script-output.txt 2>&1

Definately a script issue.

Cheers

SBK