This sort of thing usually happens when the
script writer makes too many assumptions
about cron.
The general environment that a script gets from
cron isn't the same as the one you get when
you log in.
Things to check:
- Does the script depend on being in a certain
directory to run ? ( chdir() there explicitly in the script)
- Does the script depend on certain environment variables ? cron doesn't read your ".profile" file.
The PATH environment variable is a common problem.