On Wed, 2016-08-10 at 02:52 +0000, Nakamura, Yusuke (ADITJ/SWG) wrote:
I’m working on Connman integrated in an automotive system.
I’d like to reduce the frequency of writing data to the file system
as much as possible since it requires to support long term lifecycle
and limited storage capability.
Connman always saves a keyfile to the file system
(/var/lib/connman/service_name) when it connects to an access point
Yes, please check/audit the code so that only relevant writes go to the
file. If ConnMan does other excessive writes to the file, please fix.
If the user connects to the usual access point, the key to be
in the keyfile is usually only “Modified”.
As far as I can see no one in the Connman seems to rely on this key.
Therefore I’d like to make Connman not to save the keyfile to the
file system if updated key is only “Modified”.
I have used the Modified value in a ConnMan specific shell script
sorting saved services according to last used time and deleting the not
recently used ones. As such, the Modified value is useful for
accounting/statistics purposes and I'd like to keep it. That does not
prevent you from creating a nice patch not saving the file due to the
Modified value being updated and even sending it as an RFC to the
mailing list for anyone else needing a similar solution.
What do you think?
I'd keep saving of Modified value in upstream for now, what do others