On Jan 24 23:05:59, polarian@polarian.dev wrote:
> Also ignore the clock desyncronisation, raspberry pi's do not have hardware
> clocks thus they lack the ability to keep track of time themselves and rely
> on NTP to keep a software clock updated. I have realised that ntpd struggles
> to work on raspberry pis as if the clock is too desynced it will refuse to
> resync, or will do it in a couple of second increments every hour or so,
> which would take years to resync the clock, which is a pain!
> WARNING: clock lost 320 days
> WARNING: CHECK AND RESET THE DATE!
Out of curiosity, what exactly did your ntpd do at that boot
(zgrep /var/log/daemon.?.gz for ntpd) and what time do you have
after ntpd does that?
On my RPI4, ntpd does a settime if the clock is too off;
it only does these incremental jumps if it's close enough
Jan 25 08:42:22 pi ntpd[15262]: cancel settime because offset is
negative or close enough
No comments:
Post a Comment