On Mon, 22 May 2023 at 03:42, Dave Hart <h...@ntp.org> wrote: > > After a bunch of testing myself, I’d appreciate others willing to donate > some time to try out the new code and help work out any remaining kinks. > Obviously pool clients using ntpd are prime candidates to test this. Those > running ntpd as pool servers could also help out by configuring pool > associations with noselect or using prefer on their explicitly configured > sources. > > The basic logic is that when a server has not survived for 10 consecutive > poll intervals it is a candidate to be preempted. Only the lowest-scoring > servers are removed, and only once there are already maxclock > associations. Those preempted are automatically replaced within a poll > interval or two by newly-solicited sources. > > You may want to adjust tos maxclock from its default of 10 to see how it > works combining more or less sources. >
Feedback from a helpful tester that they didn't see the removal of peers in their log prompts me to add that you might want to turn on logging of peer events in ntp.conf: logconfig +peerall Cheers, Dave Hart
