[ntp:questions] Re: ntp servers reporting leap second erroneously?
martin.burnicki at meinberg.de
Mon Oct 17 14:04:46 UTC 2005
David L. Mills wrote:
> As I said to your private message, your simulation has to include the
> actual leap; in other words, the real clock seen be the kernel has to
> step in order for the ntpd clock to follow it. I don't see means to do
> this in your simulation.
I'm not quite sure that I understand correctly what you mean.
I have a kind of radio clock which can be used as a refclock for ntpd. I do
not only set up the date and time to shortly before the time of leap second
insertion, I can also configure that device to pass the leap second
announcement to ntpd.
I have verified using ntpq that server's ntpd is correctly detecting the
leap second announcement, set its internal leap bits to 01 and also sends
leap bits 01 to the clients.
With the ntpd code from a few days ago I could see that the Linux kernel did
receive the announcement and handle it well whereas the Windows version
didn't. The current ntp-dev version doesn's seem to notify the Linux kernel
anymore, so ntpd has to do a time step some minutes later like under
More information about the questions