diff options
author | Alan Jenkins <alan.christopher.jenkins@gmail.com> | 2018-08-27 19:09:58 +0100 |
---|---|---|
committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2018-08-29 18:07:06 +0200 |
commit | 8f8112f916c68746c436c3e4314b226fee820f1e (patch) | |
tree | 9957c1b02b3be69de9b7cc409f35aa0b9270d1ae /man/resolved.conf.xml | |
parent | 9e2acd1d24a8516c94ce862e9fbf63dd8d751572 (diff) | |
download | systemd-8f8112f916c68746c436c3e4314b226fee820f1e.tar.gz |
resolve: update comment, avoid alarming wrongness
`systemd-resolved.service` runs as `User=systemd-resolved`, and uses certain
Capabilit{y,ies} magic. By my understanding, this means it is started with a
number of "privileges". Indeed, `capabilities(7)` explains
> Linux divides the privileges traditionally
> associated with superuser into distinct units, known as capabilities,
> which can be independently enabled and disabled."
This situation appears to contradict our current code comment which said
> If we are not running as root we assume all privileges are already dropped.
This appears to be a confusion in the comment only. The rest of the code
tells a much clearer story. (Don't ask me if the story is correct.
`capabilities(7)` scares me). Let's tweak the comment to make it consistent
and avoid worrying readers about this.
Diffstat (limited to 'man/resolved.conf.xml')
0 files changed, 0 insertions, 0 deletions