On 03/12/2018 03:21 PM, Andreas Koller wrote:
> You should not edit the
> hand. ConnMan will overwrite them now and then. Though you can write
> provisioning configuration file.
So there is no persistence between boots without provisioning configuration files
and changing the properties using dbus/connmanctl is meant to be temporary?
Maybe we are talking past each other. ConnMan stores the current
configuration /var/lib/connman/ethernet_MAC_cable/settings. The current
configuration means the stuff you tell ConnMan via D-Bus. Any change via
D-Bus will be stored into settings immediately. So it is persistent. If
you try to modify the settings file by hand and ConnMan is running in
the background your change will be overwritten.
On the other hand, the provisioning file is under control of the user.
So if you don't want to configure your system via D-Bus for some reason
you can use the provisioning 'interface'.
>> under /var/lib/connman/ and how can it be forced (if
> forced to what?
To create /var/lib/connman/ethernet_MAC_cable/settings files after sending configuration
changes using dbus.
Consider settings as a binary file and you should not modify yourself.
Obviously, you could create a settings file when ConnMan doesn't run but
this is not really a supported way to do things.
If not for providing persistence - what is the purpose of those
Connman doesn't seem to rely on their existence and it's unclear to me, when and
why they are written at all.
I hope I answered the question above.