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
Snip>
I just run a home desktop system, but thought I should add that I have
noticed a similar problem in 10.1. The clock has run slow ever since
install, about two years ago.
I don't yet have the knowledge to offer more info, but am following this
discussion closely in hope of learning more.
-ED-
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
