Re: [Ntp] Leap second

On Thu, Jan 23, 2020, 4:52 PM Hal Murray <hmurray@megapathdsl.net> wrote:

>
> Warner Losh said:
> > NTP timestamp repeats the last second of the day. Once without the leap
> bit
> > set and then again with it set.
>
> Which bit is that?  I don't know of a single "leap bit" in the header.
>
> There is a 2 bit header field with: normal (no leap), and add+del (leap
> pending) states.  The 4th state is used for non-in-sync.  Assuming you
> meant
> "bits" rather than bit, then the on-off is backwards.  I expect it to be
> sending leap-pending for most of the day, then send normal (no
> leap-pending)
> for the repeated last second of the day.
>
> --------
>
> I just looked at some code and found:
>                 if (leap_sec_in_progress) {
>                         /* always send "not sync" */
>                         xmt_leap = LEAP_NOTINSYNC;
>                 }
>
> Looks like it is responding with "I don't know" during the extra second.
> (but
> I didn't check carefully)
>

That was what I was thinking about...

Warner

-- 
> These are my opinions.  I hate spam.
>
>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp
>