After 30min from the leap second, I checked my NTP client box and
found something interesting.  It had 5 pool servers configured, but
one of them was unreachable, so it effectively had only four to work
with.  Two of these ran old versions of NTP (4.1.1) and probably were
not aware of the leap second, being off by almost 1s.  However, one of
them was a stratum 1 server to which the client had selected as the
primary reference.

Since the client was polling only every 1024s, it had not stepped nor
slewed the clock either way, but then it started missing a poll on the
good stratum 1 server.  Within the hour, it had decided that the new
NTP servers were correct and selected one of them as the primary
reference.

Now, were it the other way around, the client might have selected an
older NTP server and would thus get the wrong time.  I wonder if the
client should also consider the NTP server version when selecting a
reference, at least around a leap second event.

Happy 2009, especially after a long 2008.

_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.org/mailman/listinfo/questions

Reply via email to