On Jan 25, 2007, at 1:40 PM, Ryan Malayter wrote: > On 1/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Of course, you could implement a more pool specific solution >> ( just doing >> a new DNS lookup at the pool when one server goes down ) but I >> would be in >> favor of a more generic solution ( active and spare ntpd server in >> the >> config ) > > I would suggest behavior that increases maxpoll for an *unreachable* > server to at least 2**16 seconds (about once a day). It could then > re-issue DNS lookups for unreachable servers after say 2**18 seconds > of a server being unreachable.
It is likely to be helpful if the default maxpoll was increased somewhat; I know that some of the larger vendors providing their own time service (ie, time.apple.com or time.windows.com) set maxpoll to something like 17. On the other hand, I've read somewhere that the maxpoll default of 10 was chosen to balance update polling rates against the stability of the NTP PLL. In truth, it's not the people polling at once an hour or once a day that are the problem; it's the people with burst or iburst that also firewall all of my NTP replies that end up polling my servers every second or some similarlly horrendous rate that are the real problem. I don't believe that clients should query time more often than every 64 seconds (~ 1 minute) regardless of user-specified options or tuning.... -- -Chuck _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
