Quote:
Originally Posted by davidfor
On my Glo HD I can change the time with WiFi enabled and connected. The sync didn't fix the time the first time I tried, but I set it to 11 hours in the future. When I changed it by a couple of minutes, it did fix the time. It's probably using ntp and following its rules.
|
I only tried 15 minutes (900 seconds) so you're likely right about the ntp settings. I'm wondering if ntpd will exit if the difference is over 1000 seconds and need a restart to start again. I used to see that with a server where an application tried for 100% CPU and blocked a lot of background processes from running. Depending on what the DBA's were doing, the process would be kicked on on Friday around 9PM and run through the weekend. By Monday AM, the clock could be off by ~ one hour and would not automatically correct. When we investigated, we found a panic message from the ntpd logged. The "solution" was a cron job that ran the ntpd with a -g option on Monday at 6AM. Decimating the DBAs was discussed but never implemented.