Robert Smits wrote:
On December 6, 2007 05:54:39 am Carlos E. R. wrote:
The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re the
problem, what result do you get when you try setting the time manually,
as root, from the command line? You know, the old
ntpdate -u <IP-address-of-time-server>
It works, of course. That's what I'm doing every time NTP quits.
The problem is that NTP can't keep the system clock disciplined, it strays
off as soon as NTP looses the network peers, and not a second or two, but
several minutes.
It seems a kernel problem, not an NTP problem.
Actually, it looks way more like a hardware problem than a software problem.
Normally I can run any of my systems for more than a month without being more
than a minute or two off. Have you considered that the backup battery may be
low, or that you have a power supply problem?
Of course, one way to check it is if the same hardware shows different timing
problems is to reinstall 10.2 but I know what a PITA that is.
Changing the CMOS battery would be simpler, and costs less
than lunch in a restaurant.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
