[ntp:questions] Re: ntpd not adjusting time anymore

Harlan Stenn stenn at ntp.isc.org
Thu Dec 1 22:20:11 UTC 2005

'state 4' means ntpd thinks it knows the frequency offset needed to stay in
sync, and that ntpd thinks it can track time "well" and the clock is in

I believe your 'tinker step 0' is the problem.

I suspect you are losing clock interrupts somehow and with the 'step 0' ntpd
cannot correct this.  I do not know this, but it's one of the first things I
think of when I see somebody is running linux.

Also, if you are running ntpdate (or sntp) to set the clock before starting
ntpd, there is no need to start ntpd with -g.

It may be instructive to try 4.2.0 with your "stock" ntp.conf file and see
how that behaves, and then try the same experiment with a recent ntp-dev


More information about the questions mailing list