Ask Bjørn Hansen wrote:
On Aug 22, 2005, at 11:25 AM, Brad Knowles wrote:
At 6:37 PM +0200 2005-08-22, Adrian von Bidder wrote:
Actually, this is easy enough to resolve. Dr. Mills has
mentioned some additional options I had not heard of, whereby ntpd
will monitor the remote server, but won't actually use it. This
should allow you to monitor much larger groups of servers.
You've still got a scaling issue, but this should push the
problem out to measuring hundreds or maybe a thousand or more
servers, as opposed to 50-100.
If you email me the specifics off-list then I'd be interested in
trying it out. :-)
I did a small test with this, on a subset of the pool. All the servers
are defined in ntp.conf with something like :
server <ip> noselect maxpoll 6
My ntpd server (4.2.0a+stable-2 on linux 2.6.12.3) seems pretty stable
with that configuration (working for some hours now).
A small script polls "ntpq -n -c peers" every 10 seconds, and detect
servers beeing polled.
All this works pretty well. But: ntpd does not adapt the polling
interval of these "noselect" servers. The polling stick at 64s, so it
will be needed to manually set minpoll interval to something longer,
like 256 or 512s.
-- damz
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
