X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.exec.xml;h=d426ac0899a4b146d1967a24f3c9b18018de2fa0;hb=1b8689f94983b47bf190e77ddb03a8fc6af15fb3;hp=d206d4f64564210aa0cedf913f263a5da0bc1caf;hpb=70a44afee385c4afadaab9a002b3f9dd44aedf4a;p=elogind.git
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index d206d4f64..d426ac089 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -341,7 +341,7 @@
The files listed with this
directive will be read shortly before
the process is executed (more
- specifically, this means after all
+ specifically, after all
processes from a previous unit state
terminated. This means you can
generate these files in one unit
@@ -764,7 +764,7 @@
capability sets as documented in
cap_from_text3.
Note that these capability sets are
- usually influenced by the capabilities
+ usually influenced (and filtered) by the capabilities
attached to the executed file. Due to
that
CapabilityBoundingSet=
@@ -845,7 +845,7 @@
processes via
/tmp or
/var/tmp
- impossible. If this is enabled all
+ impossible. If this is enabled, all
temporary files created by a service
in these directories will be removed
after the service is stopped. Defaults
@@ -934,6 +934,68 @@
accessible).
+
+ ProtectSystem=
+
+ Takes a boolean
+ argument or
+ full. If true,
+ mounts the /usr
+ and /boot
+ directories read-only for processes
+ invoked by this unit. If set to
+ full the
+ /etc is mounted
+ read-only, too. This setting ensures
+ that any modification of the vendor
+ supplied operating system (and
+ optionally its configuration) is
+ prohibited for the service. It is
+ recommended to enable this setting for
+ all long-running services, unless they
+ are involved with system updates or
+ need to modify the operating system in
+ other ways. Note however, that
+ processes retaining the CAP_SYS_ADMIN
+ capability can undo the effect of this
+ setting. This setting is hence
+ particularly useful for daemons which
+ have this capability removed, for
+ example with
+ CapabilityBoundingSet=. Defaults
+ to off.
+
+
+
+ ProtectHome=
+
+ Takes a boolean
+ argument or
+ read-only. If true,
+ the directories
+ /home and
+ /run/user are
+ made inaccessible and empty for
+ processes invoked by this unit. If set
+ to read-only the
+ two directores are made read-only
+ instead. It is recommended to enable
+ this setting for all long-running
+ services (in particular network-facing
+ ones), to ensure they cannot get access
+ to private user data, unless the
+ services actually require access to
+ the user's private data. Note however,
+ that processes retaining the
+ CAP_SYS_ADMIN capability can undo the
+ effect of this setting. This setting
+ is hence particularly useful for
+ daemons which have this capability
+ removed, for example with
+ CapabilityBoundingSet=. Defaults
+ to off.
+
+
MountFlags=
@@ -968,6 +1030,8 @@
namespace related options
(PrivateTmp=,
PrivateDevices=,
+ ReadOnlySystem=,
+ ProtectedHome=,
ReadOnlyDirectories=,
InaccessibleDirectories=
and
@@ -1022,7 +1086,7 @@
AppArmorProfile=
- Take a profile name as argument.
+ Takes a profile name as argument.
The process executed by the unit will switch to
this profile when started. Profiles must already
be loaded in the kernel, or the unit will fail.
@@ -1208,18 +1272,18 @@
correctly on x86-64). If running in user
mode and this option is used,
NoNewPrivileges=yes
- is implied. By default no
+ is implied. By default, no
restriction applies, all address
families are accessible to
processes. If assigned the empty
- string any previous list changes are
+ string, any previous list changes are
undone.
Use this option to limit
exposure of processes to remote
systems, in particular via exotic
network protocols. Note that in most
- cases the local
+ cases, the local
AF_UNIX address
family should be included in the
configured whitelist as it is
@@ -1240,7 +1304,7 @@
x86 and
x86-64. This is
useful when running 32-bit services on
- a 64-bit host system. If not specified
+ a 64-bit host system. If not specified,
the personality is left unmodified and
thus reflects the personality of the
host system's
@@ -1252,14 +1316,14 @@
RuntimeDirectoryMode=
Takes a list of
- directory names. If set one or more
+ directory names. If set, one or more
directories by the specified names
will be created below
/run (for system
services) or below
$XDG_RUNTIME_DIR
(for user services) when the unit is
- started and removed when the unit is
+ started, and removed when the unit is
stopped. The directories will have the
access mode specified in
RuntimeDirectoryMode=,
@@ -1275,7 +1339,7 @@
/, i.e. must refer
to simple directories to create or
remove. This is particularly useful
- for unpriviliges daemons that cannot
+ for unprivileged daemons that cannot
create runtime directories in
/run due to lack
of privileges, and to make sure the
@@ -1427,7 +1491,7 @@
systemd.setenv= (see
systemd1). Additional
variables may also be set through PAM,
- c.f. pam_env8.
+ cf. pam_env8.