Hi.
I've been having a lot trouble with otimed, the clock on my FR jumps
back and forth one or two hours sometimes.
You can imagine the kind of chaos this causes in my life when I depend
on the clock and alarms of the FR....
I traveled to another timezone, and the time there was set mostly wrong.
It booted with the correct time, then after a while it had wrong hour.
Then I came back, and surprise, now the time is right for the place I
left, but not for the place I am now. :/
I think there is a problem with the determination of the timezone.
The frameworkd.log has a lot of "GSM: Multiple timezones" in it.
Can someone please explain what to do in this case?
By looking at the otimed code, I see that the only valid values for
"timesources" are "GPS,NTP", and for "zonesources" is "GSM".
It would probably make more sense to set the timezone via GPS and the
time via GSM, in my opinion... timezone changes less often than clock
time, so it is practical to launch GPS when arriving to a new timezone
to give the hint, and GPS is always right (contrary to GSM).
Anyway, I've changed /etc/timezone to "Europe/Lisbon" and put "GPS" in
"zonesources" (which is currently the same as putting "NONE") in the
hope that the FR's clock will stay within the same timezone as long as
I want.
But of course, I'd like to automated system to work...
This standard configuration is obviously not working well; what config
should I do?
Thx,
Vasco.
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
