Recent Features
| |||||||||||||
LinuxCon: Mobile network management with ConnManLinuxCon: Mobile network management with ConnManPosted Sep 1, 2011 17:34 UTC (Thu) by nix (subscriber, #2304)In reply to: LinuxCon: Mobile network management with ConnMan by njs Parent article: LinuxCon: Mobile network management with ConnMan
Ah, I thought it was a 'check time server at intervals, rather than continuously' thing. (At least, that's how all SNTP clients I've ever seen have worked. Mind you, I haven't looked at all hard.)
(Log in to post comments)
LinuxCon: Mobile network management with ConnMan Posted Sep 1, 2011 17:51 UTC (Thu) by njs (guest, #40338) [Link]
Oh, well, I just looked at the spec, so don't trust me.
Checking at intervals should work fine so long as you use the information to do some sort of drift-correction on the local clock, but I don't know if anyone does.
The ridiculous thing is that most of these devices have a GPS receiver in them, but AFAICT my phone can't be bothered to actually use that as a time reference, even when it's turned on...
LinuxCon: Mobile network management with ConnMan Posted Sep 2, 2011 23:04 UTC (Fri) by dmarti (subscriber, #11625) [Link] Does the cellular network have its own time protocol? "Dumb" phones are getting their time over the network somehow. Maybe it's available to userspace somewhere.
LinuxCon: Mobile network management with ConnMan Posted Sep 3, 2011 0:07 UTC (Sat) by mjg59 (subscriber, #23239) [Link]
Most (but not all) GSM networks send a usable time signal. I think all CDMA ones do.
LinuxCon: Mobile network management with ConnMan Posted Sep 7, 2011 23:45 UTC (Wed) by Baylink (subscriber, #755) [Link]
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.
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!
|
|||||||||||||