I have a maintenance utility that runs under cron each night at
midnight. The first thing it does is rename a log file using a
combination of current date and time. Almost without exception the
time will be 235958, but occasionally I'll get a 000001. Something
is happening on those rare occasions to delay the script three
seconds. But I am wondering why crond is starting the job two seconds
before it is scheduled? Certainly not an earth-shaking question, just
being curious.
--
Daniel Monjar (mailto:dmonjar_at_orgtek.com)
"Meddle not in the affairs of dragons,
for you are crunchy and taste good with ketchup."
Received on Tue Jul 25 2000 - 13:03:57 NZST