the implementation of the functionality is now in test from my side.
2 new methods are available via net.connman.Manager interface.
- GetKnownServices (like proposed by Marco Maniezzo)
- RemoveKnownService (which removes a given known service)
The internal tests are successful. A component test will be done these days.
How could I provide the patch for review / pull request?
From: Daniel Wagner <wagi(a)monom.org>
Sent: Monday, November 11, 2019 10:13 AM
To: Ryll, Jan (GED-SDD2) <Jan.Ryll(a)bshg.com>; connman(a)lists.01.org
Subject: Re: [RFC 1/2] Storage based service retrieval
On 08.11.19 15:00, Ryll, Jan (GED-SDD2) wrote:
this RFC seems to fit to my question "what if a wifi network service
is not available anymore and I need to remove/clear the credential /
Passphrase? How could I achieve this?".
So I read the comments and agree with Patrik. The GetKnownServices()
method should return also the currently unavailable/absent networks
for which a service folder exists.
Indeed, Patrik brings up a good point. Probably adding a call like
RemoveKnowService(Object Path) would work, where one can add a object path retrieved via
Another thing which I would like to see is GetKnownServices returning the information
stored in the settings file. Just be looking at the object path, it will be hard to figure
which known service should be deleted.
In my case there are many service folders like
This folders should be also removable after the change with the
service remove functionality.
Could this be a solution?
Yes, this sounds reasonable. A 'remove' should really clean up. So those folder
should be delete alongside.