View Single Post
Old 09-05-2013, 10:14 PM   #9
Uschiekid
Tenrec
Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.
 
Posts: 724
Karma: 1076988
Join Date: Oct 2012
Device: Kobo Aura One, Kobo Glo
Quote:
Originally Posted by DNSB View Post
It's possible that Kobo limits the maximum time change on a NTP sync. We used to have issues with a couple of Unix servers that reset to 1970-Jan-01 on an extended power outage. The NTP daemon could only correct the real time clock by plus/minus 4 hours on a sync cycle so a maximum correction of 16 hours per day with our 4 NTP syncs per 24 hours. Oddly, the operating system time and date would display the current time/date after the first sync but on a restart, the hardware clock would revert to a time and date depending on how many time sync cycles had occurred.

Regards,
David
Maybe, but every time I intentionally set my clock back (to extend a library book that I don't finish on time ) and forget to reset it, connecting to the wifi only corrects it while I'm actually connected. Then it reverts to what I set it to.
Uschiekid is offline   Reply With Quote