Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Nov 2011 19:27:28 -0400
From:      Robert Simmons <rsimmons0@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: ntpdate on boot problem
Message-ID:  <CA%2BQLa9DCL0hZF6PjmeRFE6bha9=kYW-QqL7dFtJKd=p5v0A0nA@mail.gmail.com>
In-Reply-To: <4EB5B9AF.9080101@infracaninophile.co.uk>
References:  <CA%2BQLa9BOozP544LB7MwzjvXqHPLxgfU0w_nr%2BWv9bQtexFMjbw@mail.gmail.com> <20111105220349.GA49530@freebsd.org> <CA%2BQLa9BV3DCfW4GMJEN4q1nLSJ92yRUCk_VsK-=hWWNy1d6Qng@mail.gmail.com> <4EB5B9AF.9080101@infracaninophile.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 5, 2011 at 6:33 PM, Matthew Seaman
<m.seaman@infracaninophile.co.uk> wrote:
> crontabs have this handy '@reboot' syntax... =A0It's all explained in
> crontab(5).

Thanks!

> However, you would be well advised to run ntpd(8) rather than bodging
> the clock with ntpdate at intervals. =A0ntpdate is deprecated by the ntp
> project, given that ntpd now has the capability to synch the clock the
> first time after restart no matter what the offset. =A0Just add these
> rc.conf settings:
>
> ntpd_enable=3D"YES"
> ntpd_sync_on_start=3D"YES"

Thanks again, this works without any problems.  I'm still curious how
to get the ntpdate adjustment to occur later in the boot process after
the network interface is UP, but now it's merely academic.

Rob



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9DCL0hZF6PjmeRFE6bha9=kYW-QqL7dFtJKd=p5v0A0nA>