Tom Smith wrote: > tor wrote: > >> >> I still get 2 resets an hour (depending on load ?), synchronisation >> lost and >> a large frequency (512 ppm). >> If I read the log correctly then "kernel time dicipline status change 1" >> means the kernel is now adjusting the hardware clock. >> >> Nov 1 04:45:45 lv-lomur ntpd: ntpd shutdown succeeded >> Nov 1 04:45:46 lv-lomur ntpdate[12129]: step time server 172.17.2.71 >> offset >> 0.540713 sec >> Nov 1 04:45:46 lv-lomur ntpd: succeeded >> Nov 1 04:45:46 lv-lomur ntpd[12133]: ntpd [EMAIL PROTECTED] Thu Sep 11 >> 05:38:15 >> EDT 2003 (1) >> Nov 1 04:45:46 lv-lomur ntpd: ntpd startup succeeded >> Nov 1 04:45:46 lv-lomur ntpd[12133]: precision = 9 usec >> Nov 1 04:45:46 lv-lomur ntpd[12133]: kernel time discipline status 0040 >> Nov 1 04:45:46 lv-lomur ntpd[12133]: frequency initialized 0.000 from
I'm not sure I understand what you are showing us. You appear to be shutting down ntpd running ntpdate and then starting ntpd again. Why exactly are you doing that and what are you expecting to do thereby? It is not clear why you are running ntpd v 4.1.2, you need to upgrade. It is also not clear from this what servers ntpd preferred in getting it's packets. Do you know that it was the same as 172.17.2.71? If not do you know the difference between them? Is it in your ntp configuration file? Danny _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
