Neil Dawkins wrote:
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.
Carlos,
I had a similar problem on one of my 10.3 servers.
I had to reset /sys/devices/system/clocksource/clocksource0/current_clocksource (in this case to jiffies).
To list available sources:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
Before 10.3 I have not experienced this issue.
Regards Neil
________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________
I corrected the systemclock in the BIOS and the troubles were over André den Oudsten -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org