Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


Hello,

If you add the option ProtectSystem=yes to the service file, then the
daemon will not have the ability to write to /usr.

There is no reason why it needs to write there, so enabling this
option should not cause any problems.

This option is one of the systemd security features for systemd
service files that was detailed in a talk[0] given by Lennart which
details various security features you can enable in your package's
service files.

micah

[0] http://ftp.nluug.nl/video/nluug/2014-11-20_nj14/zaal-2/5_Lennart_Poettering_-_Systemd.webm

--dhcp-script option. By making this change, those processes are going
to be invoked with read-only /usr. That's probably fine in most cases,
but there's no certainty that someone's script doesn't write /usr, and
for that script, this is a non-backwards compatible change.

Simon.