[time-nuts] future NTP programs...
Poul-Henning Kamp
phk at phk.freebsd.dk
Mon Nov 10 03:43:29 EST 2014
--------
In message <43713AD334A7485B8B0CCED799C6C19A at Alta>, "David J Taylor" writes:
>Personally, I feel that the ability to monitor the workings of an NTP
>implementation remotely is an important feature of the (present) software.
So, this is one thing I really don't understand...
You can monitor all your clients from your server if you want to,
by looing at the timestamp the client sends you.
I implemented this feature in NTPns over a decade ago (see below)
Why on Earth would anybody prefer to monitor it on each client separately
instead of getting one central unified view ?
Yes, of course you should be able to tell if your timekeeping is good
on the local machine, but I don't think the control-mode NTP packets
is a good idea.
Poul-Henning
NTPns > show ntpv4 0 partner
IP number port leap v m s p P offset refid
Max partners: 10000
total ours others
partners 2458 855 1603
partners good 1874 843 1031
partners bad 584 12 572
partners > 1s 323 5 318
partners < 1s 470 10 460
partners < 100ms 367 37 330
partners < 10ms 521 195 326
partners < 1ms 777 608 169
NTPns > show ntpv4 0 partner bad
IP number port leap v m s p P offset refid
0.0.38.89 123 no 3 3 0 0 0 -0.166501269 []
0.0.62.87 123 no 3 3 0 0 0 -0.755177799 []
0.0.10.55 123 no 1 3 0 0 0 -0.397674942 []
0.0.240.197 123 unk 4 3 0 6 -19 -3308.8 [INIT]
0.0.227.61 123 no 4 3 0 0 0 -3.024952149 []
0.0.125.188 123 no 3 3 0 0 0 0.185896998 []
0.0.145.174 123 no 3 3 0 0 0 0.465722434 []
0.0.196.133 123 no 3 3 0 0 0 -0.180700990 []
0.0.16.190 123 unk 3 3 0 10 -6 -0.520566284 []
0.0.68.26 123 no 3 3 8 6 -18 0.345824138 [CHU_AUDIO#1]
[...]
IP numbers obfuscated to protect the incompetent...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
More information about the time-nuts
mailing list