On Tue, 26 Jul 2005 10:48:07 +0100,David Reynolds wrote:
One way of doing it (probably not the most elegant way) would be to cron it. Then you can choose the update frequency yourself and be sure that it works.
Thanks for that suggestion. I had already put this measure in place, which ensured the clock was never more than half an hour off, but did cause an awful lot of checks when the clock raced towards check time, was put back and raced forwards again etc.
On Tue, 26 Jul 2005 18:39:26 +0100, Wayne Stallwood wrote:
try clock=pit or clock=pmtmr ( I think 2.6 series kernels are supposed to default to pmtmr )
Adding clock=pit to the kernel boot options worked whereas earlier suggestions such as noapic didn't. Hurray!
This was causing me a major headache since I had set up an wiki along with other services that were already being test driven by colleagues, but were being rendered semi-useless by the hyperactive system clock.
Hope that helps and welcome to the group.
Thank you, you have certainly been of help.
Best regards, Geir.