Re: ntpd vs ntpdate with no hardware clock
- Reply: bob prohaska : "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:16:34 UTC
Try -q on ntpd. It will step system time, but only once. FreeBSD will set the time to the last modification of /. At least for UFS... I'm guessing this is why it was within a minute.... and is FreeBSD's psuedo equivalent. Warner. On Sun, Jul 7, 2024, 10:01 AM 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 > > Thanks for reading, > > bob prohaska > > >