Hi,

I had two problems.
The first was indeed that the invalid-key failure was stored on disk and upon 
loading would prevent connman from autoconnecting.
The second "problem" is that I do not really like the idea of connman relying 
on the autoscan and flush behaviour of wpa_supplicant for a service to be 
removed after some time, and with it any failure associated with it.
The idea of the plugin is to have it remove a failure after a configurable time 
so it participates again in the automatic reconnect mechanism of connman.

Regards,

Thiemo


> -----Original Message-----
> From: connman [mailto:[email protected]] On Behalf Of Patrik Flykt
> Sent: 10 October 2014 12:08
> To: [email protected]
> Subject: Re: Configuration
> 
> 
>       Hi,
> 
> On Fri, 2014-10-10 at 08:52 +0000, Thiemo van Engelen wrote:
> > So what would be the preferred way?
> 
> If the problem was that the failure got saved to disk, patch 2/2 in the
> "Don't save or load service failure" patch set should do the trick. In
> addition patch 1/2 removes service failure saving, which means that once
> a service disappears, no previous error conditions will be remembered.
> 
> Cheers,
> 
>       Patrik
> 
> 
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.connman.net/mailman/listinfo/connman
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman

Reply via email to