On Tue, 2009-12-08 at 00:36 +0100, Joachim Ott wrote: > 2009/12/7 Ivo van den Maagdenberg <[email protected]>: > > Hi, > > > > What is the known way to choose my prefered candidate for 'correct' > > time (GSM, GPS, NTP)? > > > > To illustrate: when I set the system clock and the hardware clock > > (date and hwclock) to take the GPS-time as it's reference, then after > > some seconds time seems to be flipped back to GSM-time. > > Try to change the otimed-options in /etc/frameworkd.conf, use "disable > = 1" if nothing fits. > _______________________________________________ > Shr-User mailing list > [email protected] > http://lists.shr-project.org/mailman/listinfo/shr-user
GSM time is an addon protocol to the basic protocol and seems only available on some networks. As well, some carriers dont seem to handle networks across multiple timezones well using just a single time. Getting the GSM zone setting from the network is also highly suspect, though there were bugs in otimed's handing of zones at one time as well. So edit /etc/frameworkd.conf and set zoneinfo=none and remove GSM from the others settings. Also make sure you change the ntp server from the default as its somewhere in Europe and gives unstable time at least where I am. GPS time seems the most stable in that it will set the time on the Fr, no matter what it is beforehand (i.e., the hwclock is way off as happens if the battery has been out awhile, or after a messy crash) while NTP time silently fails if in that situation. With this experience, I try and use GPS at least once a day to make sure that time is accurate, and treat NTP as unreliable, even when it has a connection. I still find myself checking the FR time against other clocks/watches and get nervous if I cant compare as I have been caught too many times with it an hour or more out :( BillK _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
