Re: ntpd vs ntpdate with no hardware clock
- In reply to: Marcin Cieslak : "Re: ntpd vs ntpdate with no hardware clock"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 07 Jul 2024 19:28:11 UTC
> On Jul 7, 2024, at 12:07 PM, Marcin Cieslak <saper@saper.info> wrote: > > On Sun, 7 Jul 2024, Ronald Klop wrote: > >> I created fakertc for my rpi4. https://www.freshports.org/sysutils/fakertc/ >> >> Saves the time on shutdown and sets it back early at boot. >> >> Plus I use ntpdate together with ntpd. Works fine. > > I have question here: > > Rrecently I have removed an RTC battery > from my amd64 system and it turned out > that ntpd couldn't do anything to set the time > because the local DNS resolver failed > (I presume it was dnssec failure). > > What is the most elegant solution to > cope with such a race condition? > (DNS needs time, setting time needs DNS) I ran into this on an old MBP. See https://forums.freebsd.org/threads/when-named-stops-working-on-reboot-after-a-long-power-out.93673/ I don't have a solution. May be use ntpdate with a dotted address instead of a dns name for an ntp server?