Comment 4 for bug 879943

Thanks for the information!

I am a bit surprised by this approach, which looks weird to me. It's a service basically deciding it "owns" the content of some files without telling anyone.

In fact, I've always believed that the configuration is in text files and not in some private database format precisely to let it be modified by file editing. Furthermore there are tons of site including distribution official ones that instruct one to actively edit those text files to achieve some goals or to solve some problem and this gets simply broken by the approach taken by the software-properties service.

Shouldn't the service at least place a watch on the files to reread them and update its vision of the configuration when the files are edited?

Incidentally, where can I find info on this service, the interfaces it exposes and how to stop it from running?