Preventing ntpd from adjusting time (backwards)

[RW]

On Tue, 21 Apr 2009 20:23:14 +0200
Mel Flynn <mel.flynn+fbsd.questions at mailing.thruhere.net> wrote:

> 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 at 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 and ntpd normally  start consecutively, both way before
Dovecot. The difference is that ntpdate runs in the foreground,
blocking the boot-process for a fraction of a second, but ntpd forks-off
into the background and takes a lot longer over making its initial
correction.

If you're dead set against using ntpdate, you could use the preferred
ntpd -gnq in it's place, at the expense of about 10 seconds of extra
boot time.