Date: Tue, 21 Apr 2009 20:23:14 +0200 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Cc: RW <rwmaillists@googlemail.com> Subject: Re: Preventing ntpd from adjusting time (backwards) Message-ID: <200904212023.14365.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <20090421183133.4e0c414f@gumby.homeunix.com> References: <200904211106.01965.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <200904211643.32448.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <20090421183133.4e0c414f@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 21 April 2009 19:31:33 RW wrote: > On Tue, 21 Apr 2009 16:43:32 +0200 > > Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> wrote: > > On Tuesday 21 April 2009 16:20:52 RW wrote: > > > The bottom line though, is that ntpdate_enable=yes solves the > > > problem entirely, since the real problem is not the step, but the > > > fact that it happens in the background, and after a delay. > > > > Care to expand on that? Dovecot won't stop if root issues a date > > command that sets time to the past, for example? > > I was assuming that since you're running ntpd you wouldn't be doing > that. Right, then this works because ntpdate is started before dovecot in rcorder, like Tim Judd said else in thread. > > > ntpdate may be deprecated, but it's been deprecated for years, and I > > > doubt it will go away until ntpd fully replaces it's functionality. > > > ntpd -gq can replace ntpdate in a crontab, but ntpd -gqn doesn't > > > really replace ntpdate -b in the boot-sequence. > > > > I'm actually counting on it to be gone in 8.0. > > Is that official? Nope, but 3 major releases of mourning should be enough ya think? Maybe not, given the problems above. Now I'm also wondering how ntpd handles securelevel 2. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904212023.14365.mel.flynn%2Bfbsd.questions>