 |
 |
> The most reliable ntp server on campus seems to be gpu.utcs.utoronto.ca. > I been tracking the performance and reliability of npt.astro for the last > one year or so and think that its lacking a lot. Gpu tracks two primary > servers including ntp.astro (because it claims to be the only primary in > the campus) and two secondaries. Heres a peer list: > >remote refid st t when poll reach delay offset disp >============================================================================== >*ntp.on.canet.ca .GPS. 1 u 304 512 377 24.80 -1.465 10.13 >+MERCURY.CS.UREG ncar.ucar.edu 2 u 318 512 377 137.01 2.489 11.83 > ntp.astro .WWV. 1 u 841 1024 377 9.98 144967. 1371.25 >+madhaus.utcs ntp.on.canet.ca 2 u 416 512 236 13.03 -3.401 256.33 Not true. ntp.astro WAS a fine server. In my comparisons with other Stratum 1 servers it gave acceptable performance when you factor in things like clocks, CPUs, network hops and such. Once ntp.astro settles down, I'll be working with Mike Peterson over at UTC to straighten out ntp.on.canet.ca It might be slightly mis-configured. It's been consistently off. In theory, it should be the best time server on campus, but it isn't. P.S. If that's the peer list for gpu then it's probably wrong. As I understand it madhaus gets its time from ntp.on.canet.ca There's no point in getting time twice from the same source. -- ================= The hardest thing to see | Tom Glinos @ U of Toronto Statistics is the way things REALLY are. | [log in to unmask]