View Single Post
Old 10-27-2016, 11:30 PM   #63
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by DNSB View Post
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.
It looks like they run ntpd with "-q" whenever the DHCP lease is acquired or changed somehow. And that means it shouldn't change the clock if it is more than 1000 seconds out.

Doing it this way also explains one of the things I saw. One of my tests didn't adjust the clock, but I changed it while the WiFi was active and it would have had a lease. When I turned WiFi off and on, the time was adjusted.

Anyway, a lot more than we need to know. I think the important things are:

- Connecting to WiFi will fix the time if it is less than 1000 seconds out.
- Using OverDrive requires an accurate clock and doesn't let you manually change it.
davidfor is offline   Reply With Quote