Date: Sun, 7 Jul 2024 09:23:51 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: ntpd vs ntpdate with no hardware clock Message-ID: <663B8441-A84B-481A-95D6-D22EDC4E66A3@yahoo.com> In-Reply-To: <Zoq7xD2BRT6YyF6l@www.zefox.net> References: <Zoq7xD2BRT6YyF6l@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 7, 2024, at 09:01, bob prohaska <fbsd@www.zefox.net> wrote:
> Just tried using ntpd with a fresh 14.1 installation on a Pi4.
> Near as I can tell, ntpd reports a failure due to the clock
> being off by too much, even if it's set manually to within
> a minute before reboot. Probably that's caused by the lack
> of a hardware clock on the Pi4, linux has a bodge called
> fake-hwclock. Is there an equivalent workaround for FreeBSD?
>=20
> In the meantime ntpdate seems to work, though deprecated
FYI: my /etc/rc.conf for media sometimes used on such
hardware has:
ntpd_enable=3D"YES"
ntpd_sync_on_start=3D"YES"
ntpd_user=3D"root"
"man 5 rc.conf" reports about ntpd_sync_on_start :
ntpd_sync_on_start
(bool) If set to =E2=80=9CYES=E2=80=9D, ntpd(8) is run =
with the -g flag,
which syncs the system's clock on startup. See ntpd(8) =
for
more information regarding the -g option. This is a
preferred alternative to using ntpdate(8) or specifying =
the
ntpdate_enable variable.
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?663B8441-A84B-481A-95D6-D22EDC4E66A3>