schwurbel wrote:
How could that excessive offset happen in the first place?
And why would the program deny setting the time when the offset is so wrong? Isn’t correcting the time the point of this program? Weird.
The hardware clock in the box has a battery backup. So I have a few theories:
-
The battery has failed and the RTC is drifting wildly.
-
The clock came from the factory way out of sync.
-
The box has been off network for a LONG time and the RTC has drifted.
The reason it won’t sync is because that’s the standard. If the hardware clock is more than a certain amount of time off from the NTP clock, the software assumes it’s the NTP clock that’s wrong. NTP clocks *can* (and often are) wrong… so that prevents an excessive shift in time.
I can’t imagine only 1 minute 18 seconds being enough to do that, though…
