Date: Sat, 1 Jan 2000 12:02:00 -0800 (PST) From: John Polstra <jdp@polstra.com> To: roberto@keltia.freenix.fr Cc: current@freebsd.org Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <200001012002.MAA45455@vashon.polstra.com> In-Reply-To: <20000101194118.A19381@keltia.freenix.fr> References: <19991231225535.A8004@Denninger.Net> <20000101113750.B89903@Denninger.Net> <200001011747.JAA45272@vashon.polstra.com> <20000101194118.A19381@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20000101194118.A19381@keltia.freenix.fr>, Ollivier Robert <roberto@keltia.freenix.fr> wrote: > According to John Polstra: > > Current versions of ntpd use these features if they're available. I > > The ntpd daemon in -CURRENT doesn't use these as we cannot be sure the user > has enabled them. I don't understand why they're disabled in -current. Empirically, it appears that the standard ntpd (from the port) still works fine if the features aren't in the kernel. It emits a warning at start-up time, but then it runs fine after that. > We should make them standard IMO. I agree. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001012002.MAA45455>