[ntp:questions] Re: ntp servers reporting leap second erroneously?
martin.burnicki at meinberg.de
Mon Oct 24 22:43:01 UTC 2005
David L. Mills wrote:
> Let's face it, the version you are using has a bug, since corrected in
> ntp-dev. Dirty rotten gmtime() numbers the days of the month from zero,
> not one. I can verify here that the kernel does get the ntp_adjtime()
> update on the correct month and day and does the right thing. I don't
> have the test setup you have to actually verify the intended behavior.
> Please report.
As already reported on bugzilla under
I've run the leap second test once again with the current ntp-dev (patch
level 1.1423) under Linux and Windows and found that it works now as
Under Linux, the leap second announcement is passed to the kernel which
handles it properly.
Under Windows, the time is stepped back by one second a few minutes after
the time of leap second insertion.
Of course the latter is not optimal and I'd appreciate if ntpd could do the
slewing of the system clock on systems where the kernel clock is not aware
of leap seconds.
As I've reported earlier on this news group even the Windows w32time service
is capable to slew the Windows system clock at UTC midnight to compensate
the leap second offset in just a few seconds.
More information about the questions