Re: ntpd vs ntpdate with no hardware clock
- Reply: Warner Losh : "Re: ntpd vs ntpdate with no hardware clock"
- In reply to: bob prohaska : "ntpd vs ntpdate with no hardware clock"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 07 Jul 2024 16:23:51 UTC
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? > > In the meantime ntpdate seems to work, though deprecated FYI: my /etc/rc.conf for media sometimes used on such hardware has: ntpd_enable="YES" ntpd_sync_on_start="YES" ntpd_user="root" "man 5 rc.conf" reports about ntpd_sync_on_start : ntpd_sync_on_start (bool) If set to “YES”, 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. === Mark Millard marklmi at yahoo.com