systemd unit: ReadWritePaths semantically not best choice

[paulmenzel]

User damjan in #systemd@irc.freenode.net commented, that instead of ReadWritePaths=, one of the directives below could be used depending on the type of data.

1. StateDirectory=
2. RuntimeDirectory=
3. CacheDirectory=

Then systemctl clean UNIT would also work.

[Maryse47]

StateDirectory/RuntimeDirectory are already used in service but they aren't interchangeable with currently set ReadWritePaths (see comments in #477 ). I don't see better choice right now.

[ArchangeGabriel]

@paulmenzel Was the IRC user specifically writing about unbound? Because the way things work, the current file is perfectly fine and there nothing that can be done better to the best of my knowledge.

[paulmenzel]

As far as I remember, the current behavior of using /etc stands in the way of making Unbound more “standards compliant”.

[ArchangeGabriel]

Using /etc for what? For unbound.conf, that’s the expected spot AFAIK. For storing the root key maybe not, but this is heavily linked to the way chrooting is done AFAICS (needing the root key file and the config file in the chroot). This could be changed by using systemd for chrooting (and its automagic for bindmounting relevant files/path) I think, but might require adjustment for systems without systemd.