Date: Tue, 21 Apr 2009 16:43:32 +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: <200904211643.32448.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <20090421152052.0e6d6916@gumby.homeunix.com> References: <200904211106.01965.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <200904211409.09360.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <20090421152052.0e6d6916@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? > 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. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904211643.32448.mel.flynn%2Bfbsd.questions>