Autor: segfault Data: Para: The Tails public development discussion list Assunto: Re: [Tails-dev] Persistent torrc [Was: Tails Server: updated plan
and GSoC!]
anonym:
[...] >> Just to clarify things: Currently Tails Server does have a configuration
>> file for each service (which is made persistent if the service is
>> persistent). Those are currently in /usr/share/tails-server/options/,
>> e.g. /usr/share/tails-server/options/mumble. But I only store options in
>> there which are not part of some other configuration file, in order to
>> prevent redundancy and inconsistent states. So everytime Tails Server
>> needs the value of an user option, the corresponding configuration file
>> (e.g. /etc/mumble-server.ini for the server password) is parsed.
>> (But the persistent option is not stored anywhere else, so it is stored
>> in this internal options file.)
>>
>> Please tell me if you see any problems with this approach.
>
> Yes, this is exactly what we had very good reason to agree to do before,
> so it's awesome!
I just noticed that actually I do not parse the config files every time
I need an option value. I only read the value the first time I need it
and then store it in a variable. I do write to the config files
everytime the value is set though.
I can test later how much the performance impact of parsing the config
files every time.
