[ntp:questions] Ginormous offset and slow convergance

Pete Ashdown pashdown at xmission.com
Wed Nov 30 17:04:57 UTC 2011

=?utf-8?Q?Miguel_Gon=C3=A7alves?= <mail at miguelgoncalves.com> writes:

>On 30/11/2011, at 15:41, Pete Ashdown <pashdown at xmission.com> wrote:

>> David Woolley <david at ex.djwhome.demon.invalid> writes:
>>> Richard B. Gilbert wrote:
>>>> On 11/29/2011 1:42 PM, Pete Ashdown wrote:
>>>>> +time-C.timefreq .ACTS.           1 u   19   64  377   37.887  
>>>>> -16011.   0.122
>>>>> Is there anything I can do to decrease the convergence time?
>>>> Little or nothing!  NTPD can, and sometimes does, take ten hours to 
>>>> reach "steady state".  It needs about thirty minutes to find a 
>>> 16 second excursions are not the result of ntpd convergence delays. 
>>> They indicate something seriously broken.  Possibly something else is 
>>> trying to set the time.
>> Thanks for the pointer David.  I added the local hardware clock (
>> to the ntp.conf and that nailed it down.  Now my convergence is under a
>> minute!

>Isn't this a Bad Idea? I mean, adding

>In none of my 3 stratum 1 servers I have this driver and they work fine. One of them is an Oncore UT+. The others are a Garmin 18 LVC and a Sure board.

>NTP gurus, what's your opinion?

For what it is worth, I fudged the stratum of to 10 and it appears
that it is only polled on the startup of ntpd.

More information about the questions mailing list