Mailinglist Archive: opensuse (3166 mails)

[Bob Berman <rjberman@xxxxxxxxxxxxx>]

I am running cron and ntp. Both run fine by themselves, but I've discovered 
that cron seems
to really hate having time changed out from under it. Or that's my guess 
anyway.

What is happening is that I have one job that is cronned to run every 5 
minutes, but if I have
ntp running, this particular cron job can miss quite a few runs - sometimes 
3 hrs. worth before
it mysteriously starts up again by itself. Another job is cronned to run at 
5AM, yet sometimes
it goes off at 4:09AM (or any other time in the early morning for that 
matter) and sometimes it
goes off right at 5:00AM!

For the job that is cronned to run every 5 minutes, if I restart cron, it 
goes off every 5 minutes
like clockwork for maybe 20-30 minutes before it stalls out. Then maybe a 
few hours later it might
run a few times.

So I'm guessing that the problem is that cron doesn't like ntp resettting 
the time. My clock doesn't
drift that badly - probably no worse than anyone else's. Has anyone else 
noticed this problem?
What do you do to solve it? I'd like to have accurate time and cron, but I 
guess I can't have both.
Any ideas? Is there any cron out there besides Vixie cron that works better 
with ntp?

(I'm on SuSE 8.0, default cron and ntp )