larry price wrote:
two possibilities,
resource contention - something else is happening and the cron job
fails before doing anything.
synchronisation issues - your clock is so off and you are using
ntpdate and every once in a while you skip over the correct time
If it's the first you should be getting some spew in your log files.
checked the spew and all looks kosher i.e. output of 'bad' cron looks
identical to 'good' cron.
Contention... hmmm... I'll change the time to some oddball minute rather
than mult of 5 and see if that does the trick...
Thanks,
mj
Matthew S. Jarvis
IT Manager
Bike Friday - "Performance that Packs."
www.bikefriday.com
541/687-0487 x140
[EMAIL PROTECTED]
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
