> Mostly because ntpd doesn't let you remove and add servers "online",
> so it'd take longer to add a new server to the monitoring. For the
> future distributed monitoring I'm planning to set it up that way though.
Huh? Yes, it does!
If, like me, you set up "requestkey" in ntp.conf according to the docs
and couldn't get it to work, the trick is that the key *also* has to be
listed as a trustedkey.
With that, I can add and remove servers on the fly.
ntpdc> keyid 2
ntpdc> passwd
MD5 Password:
ntpdc> addpeer 69.10.36.6
done!
ntpdc> pe
remote local st poll reach delay offset disp
=======================================================================
[snip]
+69.10.36.6 192.35.100.1 16 64 0 0.00000 0.000000 4.00000
A minute later, it's:
+69.10.36.6 192.35.100.1 2 64 1 0.06841 -0.004453 2.81735
Or, to use ntpq (repeated queries compressed in this display):
remote refid st t when poll reach delay offset jitter
==============================================================================
[snip]
69.10.36.6 208.184.49.9 2 u 59 64 1 68.417 -4.453 0.002
69.10.36.6 208.184.49.9 2 u 25 64 3 68.300 -4.192 0.261
69.10.36.6 208.184.49.9 2 u 1 64 7 68.300 -4.192 0.261
69.10.36.6 208.184.49.9 2 u 33 64 17 68.300 -4.192 0.435
-69.10.36.6 208.184.49.9 2 u 19 64 37 68.300 -4.192 1.077
-69.10.36.6 208.184.49.9 2 u 9 64 77 68.300 -4.192 0.964
-69.10.36.6 208.184.49.9 2 u 9 64 77 68.300 -4.192 0.964
-69.10.36.6 208.184.49.9 2 u 16 64 177 68.300 -4.192 0.886
-69.10.36.6 208.184.49.9 2 u 52 64 377 68.300 -4.192 0.810
-69.10.36.6 208.184.49.9 2 u 43 64 377 68.300 -4.192 0.811
Anyway, that's enough, so
ntpdc> unconfig 69.10.36.6
done!
ntpdc> unconfig 69.10.36.6
***Server reports data not found
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
