You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One possible theory is that the NTP client set the system time based on a misconfigured NTP pool server. Maybe we should always query 3 NTP servers and set the time only if 2 of them are within a 5s window of each other.
stapelberg
changed the title
apu hardware clock weirdness
system clock weirdness
Dec 25, 2018
From my most recent boot:
The time being way off resulted in an update not succeeding:
Note that the expiration timestamp is in the future.
Not sure what’s happening here. We’re setting the RTC in https://github.com/gokrazy/gokrazy/blob/2216841c80ef508f43b5b742ff423124f965f868/cmd/ntp/rtc.go
The text was updated successfully, but these errors were encountered: