[ntp:questions] Intended design: leap bits 00 during freq_mode?

David Mills mills at udel.edu
Tue Apr 7 20:29:57 UTC 2009


The leap bits are set the first time a valid update is received and the 
clock is set. If the NMEA driver provides thethat  update, it will set 
the server leap bits. The leap value 11 is set only before first 
synchronized and never set back to that value after that. Whether or not 
in FREQ state has nothing to do with leap bits.


Dave Hart wrote:

>Someone has observed that they get different behavior on 4.2.5p161
>regarding the leap bits during freq_mode depending on whether they
>configure a refclock (NMEA in this case) or not.  With network
>upstream servers configured, they observe leap=00 shortly after
>starting, during the frequency drift calculation.  Add a refclock, and
>leap stays 11 (sync_alarm) until the transition from freq_mode to
>My guess is the latter behavior is intended and the early clearing of
>the leap bits in freq_mode is a bug.  But I don't want to guess
>anymore :)
>Dave Hart
>questions mailing list
>questions at lists.ntp.org

More information about the questions mailing list