| |||||||||||||
LinuxCon: Mobile network management with ConnManLinuxCon: Mobile network management with ConnManPosted Sep 7, 2011 23:45 UTC (Wed) by Baylink (subscriber, #755)In reply to: LinuxCon: Mobile network management with ConnMan by njs Parent article: LinuxCon: Mobile network management with ConnMan
Don't, in fact, trust njs, nix: you're right. Using SNTP as a client to sync your clock is a "sync now, and pray the local clock's disciplined" approach, and fails for all the reasons you think it ought to.
Running a local ntpd is a Very Good Idea, even on a laptop or cellphone; it's not like it sucks a lot of cycles.
(Log in to post comments)
LinuxCon: Mobile network management with ConnMan Posted Sep 8, 2011 0:53 UTC (Thu) by nix (subscriber, #2304) [Link]
Yeah. Though good god ntpd has a lot of failure modes. I just noticed another one: suspend a machine for twelve hours or so, so its awful hardware clock has to take the burden of keeping time, then resume it. ntpd silently decides that the time has drifted too far for slewing to work, and decides that it is best to do nothing. Log anything? Of course it doesn't log anything, why would you care that your time is suddenly not synchronized!
Gah!
|
|||||||||||||