Tapio,
The kernel modifications were after rfc-1305 on NTPv3 was published. I
described what the current ntpd does. The issue is not "processing"them,
but passing them along to dependent clients, who may have an poll
interval of over a day. Presumably, the current rewrite for NTPv4 will
make these points wickedly clear.
Dave
Tapio Sokura wrote:
David L. Mills wrote:
The leap bits are set when the timing source, either modem, radio or
server, set them. However, they are provided to the kernel only on the
day of the leap.
A clarification: are you talking about the protocol (NTP) or the
implementation (ntpd), or both? I guess it is sensible for an
implementation of NTP to "process" the leap bits only on those two days
of the year leap seconds can occur, but the RFCs are a bit vague on
that. They just talk about setting the bits on the day of insertion. But
don't worry, I won't lose my sleep over this :)
Tapio
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
