Re: NTP behavior in Australia

[Poul-Henning Kamp]

In message [EMAIL PROTECTED], Steve Allen writes:
Here is one indication of NTP response to the presence of low stratum
servers which did not behave well.

http://members.iinet.net.au/~nathanael/ntpd/leap-second.html

I grabbed a set if IP#'s from pool.ntp.org and monitored them in the 24
hours before and 8 hours after the leap.

Out of a set of 12 IP#'s two public stratum 1 servers never set the
leap bit, but did apply the leapsecond locally.

One of the 12 was a stratum 1 using DCF signal, and that one as expected
only set the leap warning one hour before the event.

Ten hours after the event, two stratum 3 servers in the set still had
the leap warning bits set.

--
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

Re: NTP behavior in Australia

[David Malone]

 I grabbed a set if IP#'s from pool.ntp.org and monitored them in the 24
 hours before and 8 hours after the leap.

I did something similar using the public NTP server lists on the
ntp wiki. I'm still collecting the data, but I have some plots of
what's happening with the leap bits at:

http://www.maths.tcd.ie/~dwmalone/time/leap2005.html

It wasn't really until 24 hours before that a significant number
of servers were advertising the leap, peaking in the last measurement
before the leap. Interestingly, one server actually advertised a
leap in the wrong direction!

After the leap it looks like more stratum 1 servers were unsynchronised
than usual, though that seems to have setteled down a bit now. The
number of people with the leap bits set is dropping, but isn't quite
zero yet.

I have the peers information from out local ntp server around the
leap.  Our server did the right thing, but it looks like there were
a number of others that didn't. I haven't figured out how to visualise
that yet.

David.