Date: Sat, 23 Jun 2018 02:21:07 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 210245] [PATCH] Update etc/ntp.conf to eliminate failure modes and reflect current ntpd functionality Message-ID: <bug-210245-227-1MHnMbL7mj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210245-227@https.bugs.freebsd.org/bugzilla/> References: <bug-210245-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210245 Ian Lepore <ian@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |ian@FreeBSD.org Status|New |In Progress CC| |ian@FreeBSD.org --- Comment #2 from Ian Lepore <ian@FreeBSD.org> --- I just stumbled across this; I updated ntp.conf to use the pool keyword last year, without realizing this PR was here. I didn't realize until finding t= his that the -4/-6 flags had become meaningless in ntp.conf. I've opened a phabricator review to make that part of your changes to ntp.conf It turns out that it is also no longer necessary to use the 'preempt' keywo= rd on pool statements. Associations mobilized via pools are automatically preemptable in exactly the same way as those mobilized via manycast. I verified that our current ntp.conf pool statement behaves this way by adding ipfw rules to block packets from all the servers shown by ntpq -p. As they became unreachable the associations were dropped and new ones were mobilize= d to keep at least the number of good peers set by 'tos minclock'. https://reviews.freebsd.org/D15974 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210245-227-1MHnMbL7mj>