[ntp:questions] Very large offset and jitter values after reboot

Richard B. Gilbert rgilbert88 at comcast.net
Mon Aug 25 00:14:33 UTC 2008

Nicola Berndt wrote:
>>>     remote           refid      st t when poll reach   delay   offset  
>>> GPS_NMEA(0)     .GPS.            0 l    9   64   37    0.000  -580.75 
>>You've not had your first 8 samples yet.  You haven't actually had 
>>enough for ntpd to act on the data.  You can speed that up with iburst, 
>>but ntpd will still take a long time to get a very tight lock.  jitter 
>>will reduce as you get to the eight samples.  The good? think, is that 
>>you are more than 128ms out, so that ntpd will step the time, to zero 
>>the offset, once it gets enough samples.
> Just tried the iburst option, but I had to figure it only works with the 
> server command, not on refclocks.
> What really puzzles me, is the stoical 600 ms offset after rebooting. 
> Since it is always returning having more or less the same amount, I 
> should really be able to get rid of it, no?

600 ms seems to be a large error for a warm start.  Are you using "-g" 
to start ntpd?  Forgive me if this has already been asked and answered.

More information about the questions mailing list