On Mon, 30 Jan 2006, Niek <[EMAIL PROTECTED]> wrote:
On 1/30/2006 5:13 PM +0100, Tony Hoyle wrote:
Maybe it's not officially launched yet.. I consistently get an
offset of 8 ms for its timeservers. I guess they're not syncing off
atomic clocks or anything at that accuracy..
Tony
Tony,
ntptrace ntp1.npl.co.uk
ntp1.npl.co.uk: stratum 2, offset -0.003091, root distance 0.009232
139.143.49.18: timed out, nothing received
same for ntp2
whois 139.143.49.18
...
netname: DTINPL
descr: NPL Management Ltd
...
So they sync their prublic ntp boxes to an internal one.
From http://www.npl.co.uk/time/computer_time_service/user_guide_its.pdf :
"NPL operates two NTP servers that provide Internet Time Service to users
outside NPL. The servers are synchronised using NTP over the NPL local area
network to two other servers, which are themselves synchronised to 1
pulse-per-second signals derived from NPLs atomic clocks. The public servers
are therefore classed as stratum 2, but they are controlled by a highly
reliable source of time the UK national time scale UTC(NPL) - that is
traceable directly to UTC and independent of GPS."
I must say, things don't look great:
ntpq -p ntp1.npl.co.uk
remote refid st t when poll reach delay offset jitter
==============================================================================
LOCAL(0) .GPS. 0 - - 64 0 0.000 0.000 0.000
*139.143.49.13 .1PPS. 1 - 52 64 357 9.230 -8.911 4.270
+139.143.49.18 .1PPS. 1 - 21 64 377 9.231 -8.447 1.395
There looks to be something wrong if two time sources are close to each other,
but the machine itself is >8ms out.
--
Chris Hastie
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
