I remember back in '99 when Damon Parker wrote:
> I am running them as root through cron. The cron log even shows that they
> ran but my pages are being updated.
I bet it's a path/environment problem. Methinks that cron jobs may
not have a full environment set up when they run. This can manifest
itself in two ways: Either you try to execute something that is
in a funny directory and the shell can't find it since it doesn't
have a big path set up, or some program you run requires an environment
variable usually initialized in your login environment (or the /etc/
shell startup files).
I'm not sure if the problem would manifest itself as an output error,
but some cron installations will send mail to the cron job's owner
if the program wrtes anything out to stdout / stderr. You might
want to check to see if you have this enabled, and if so you could
always instrument your script with strategic echo's:
echo "starting cron job"
.. do step A
echo "finished a"
.. do step B
echo "finished b"
Matt
--
/* Matt Sayler -- [EMAIL PROTECTED] -- atwork?astronomy:cs
http://www.cs.utexas.edu/users/mpsayler -- (512)471-7450
Have you ever imagined a world with no hypothetical situations? */
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
