summaryrefslogtreecommitdiff
path: root/man/systemd-mount.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2017-06-28 19:29:45 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2017-06-28 13:29:45 -0400
commit0d787d5ff812bc038384ff39f8b1d64f6c2ed13f (patch)
tree63e0fbd230b0736f630c4be1e5d437af07f43aa7 /man/systemd-mount.xml
parent1f47f5504c3ecf62afc6511a48886232f39431ab (diff)
downloadsystemd-0d787d5ff812bc038384ff39f8b1d64f6c2ed13f.tar.gz
Only drop the capabilities from the bounding set if we are running as PID1 (#6204)
The CapabilityBoundingSet option only makes sense if we are running as PID1. The system.conf.d(5) manpage, already states that the CapabilityBoundingSet option: Controls which capabilities to include in the capability bounding set for PID 1 and its children. https://github.com/systemd/systemd/issues/6080
Diffstat (limited to 'man/systemd-mount.xml')
0 files changed, 0 insertions, 0 deletions