You are not logged in.
Pages: 1
Hi there!
Im glad to join you.
So... here is my prob.
Im running openntpd on every boot and my clock Syncs fine BUT my clock is running ahead of time unless I restart the deamon OR reboot the machine.
My clock runs ahead of time by about 15-20mins/day.
I wonder if this is a kernel bug or I just configured my machine in a wrong way.
Any ideas?
Cheers!
Zaxariadis
Offline
Try adding "clock=pit" to your kernel command line (in menu.lst or grub boot menu) .
1000
Offline
If that doesn't work for you (I'm having similar problems) then you might want to try ntpd instead of openntpd. I still have problems with ntpd, but not on as large a scale as openntpd.
Offline
So far so good!
"clock=pit" seams that works for me.
I google around "clock=pit" and I found that:
http://support.microsoft.com/kb/918461
"To resolve this issue, add the "clock=pit" parameter to the Linux bootloader file. The clock=pit parameter causes the Linux 2.6 kernel to use a more efficient algorithm to synchronize time between the virtual machine and the host computer. This algorithm does not adjust for lost ticks. Therefore, the algorithm does not cause the virtual machine to gain time."
Thank you all for your help!
Offline
Good to hear. I might be wrong, but I think they changed it from "clock=pit" to "clocksource=pit" in the newer kernels (2.6.20+?). Have a look at dmesg|grep -i clock and see if it's giving you a note about it.
Offline
Yap! You are right
[root@localhost zaxariadis]# dmesg|grep -i clock
Kernel command line: root=/dev/hdb1 ro clock=pit vga=771
Warning! clock= boot option is deprecated. Use clocksource=xyz
Time: pit clocksource has been installed.
Real Time Clock Driver v1.12ac
thanx
Offline
Pages: 1