andygoblins <[email protected]> wrote: > Ever since updating to 6.8, I've had trouble with the system clock not > getting set on boot. > > I know the easy answer is to script a call to rdate, but that feels like a > bandaid solution. > > I'm running from an EdgeRouter Lite (octeon) that afaik does not have a > persistent clock. Before 6.8, I always saw boot messages about how the kernel > was going to set the clock based on the filesystem. I don't see those > messages anymore, and instead see an ominous "WARNING: CHECK AND RESET THE > DATE!" > > I assume there's been some changes into how dates and time are handled, but I > haven't seen anything in the release notes. > > Can anyone point me in the right direction, or have a better bandaid idea > than calling rdate?
ntpd is run by default, and magically will correct the time almost immediately. Some significant effort went into this a few years ago. However, the kernel message will always be there. You can ignore it. Run ntpctl -s all, and you'll see the time has been corrected before significant daemons start.
