Discussion:
Manual TimeUpdates conf setting
(too old to reply)
Mike Purvis
2015-10-06 20:28:47 UTC
Permalink
Hey all,

I saw CM-631 and the clock-api.txt document, but that appears to be
referring to the dbus api. Is there something I can put in main.conf
(or elsewhere?) that will disable the ntp syncing behaviour?

Thanks,

Mike
Mike Purvis
2015-10-06 23:51:14 UTC
Permalink
Post by Mike Purvis
I saw CM-631 and the clock-api.txt document, but that appears to be
referring to the dbus api. Is there something I can put in main.conf
(or elsewhere?) that will disable the ntp syncing behaviour?
Oh yuck. I'm really hoping that this mess isn't the answer:

https://build.tizen.org/package/view_file?expand=1&file=0003-Add-systemd-service-to-manage-ConnMan-NTP-feature-TZ.patch&package=connman&project=Tizen%3AIVI&rev=9ce227c8b55355711dacd3f711e1fe71
Patrik Flykt
2015-10-08 08:23:54 UTC
Permalink
Hi,
Post by Mike Purvis
Post by Mike Purvis
I saw CM-631 and the clock-api.txt document, but that appears to be
referring to the dbus api. Is there something I can put in main.conf
(or elsewhere?) that will disable the ntp syncing behaviour?
There isn't a main.conf option for this.

The current behavior is a bit of a balancing act. Most people want all
bells and whistles to work automatically, including keeping time if the
network reports what NTP servers to use, which they more or less all do
nowadays.

A minority of people want to use some other NTP application for various
reasons I don't know about and which they don't usually tell either. For
these, there are basically three options: disable NTP once from the
Clock API, start the other NTP daemon before ConnMan or record what the
settings file looks like after disabled NTP and add that to their image
creation. The first option is the easiest, but requires user
intervention once after the first boot. The second is ok, ConnMan by
default logs an error for this and continues. And the third one I did
not tell you about.

By default ConnMan is assumed to be used in a device that
semi-frequently changes IP networks. If some other timeserver daemon is
needed, the problem becomes how to communicate the updated NTP server
list to that other daemon. The other assumption of always using a
predefined set of NTP servers for every network connected to and having
higher precision requirements than ConnMan's SNTP implementation sounds
like an exception to an exception if you ask me.

So either the NTP daemon needs to listen to ConnMan's service API
signalling, or a plugin in ConnMan needs to be created to update the
daemon via D-Bus. In the latter case ConnMan needs to understand that
someone else is in charge of NTP, which causes other modifications to
the current code.
Post by Mike Purvis
https://build.tizen.org/package/view_file?expand=1&file=0003-Add-systemd-service-to-manage-ConnMan-NTP-feature-TZ.patch&package=connman&project=Tizen%3AIVI&rev=9ce227c8b55355711dacd3f711e1fe71
I hope not, unless you're truly desperate :-)

Cheers,

Patrik

Loading...