Thread: clock problem
View Single Post
Old 02-07-2018, 06:16 PM   #10
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 Richwood View Post
Then I would think that the problem would affect every Kobo using that sync info which should be affecting every Kobo in an area of France or possibly the whole country. Syncing presumably goes through a Kobo central server for a large area.
I doubt they are syncing the time with their servers. I would expect they are using a generic ntp pool. But, I would expect that to be correct.
davidfor is offline   Reply With Quote