X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.exec.xml;h=a1eb1127d965bd289418bb116ecc671175f78d45;hb=59b8f6b628145586e87b8a4f6e29c755ad7d61ed;hp=22f076870f6f777ca3cbedf70e70d24b916c1471;hpb=b8bde11658366290521e3d03316378b482600323;p=elogind.git
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 22f076870..a1eb1127d 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -103,7 +103,7 @@
directory path. Sets the root
directory for executed processes, with
the
- chroot2
+ chroot2
system call. If this is used, it must
be ensured that the process and all
its auxiliary files are available in
@@ -304,7 +304,7 @@
See
- environ7
+ environ7
for details about environment variables.
@@ -443,12 +443,12 @@
for other processes to release the
terminal.
connects standard output to the
- syslog3
+ syslog3
system syslog
service.
connects it with the kernel log buffer
which is accessible via
- dmesg1.
+ dmesg1.
connects it with the journal which is
accessible via
journalctl1
@@ -568,7 +568,7 @@
,
or
. See
- syslog3
+ syslog3
for details. This option is only
useful when
StandardOutput= or
@@ -590,7 +590,7 @@
,
,
. See
- syslog3
+ syslog3
for details. This option is only
useful when
StandardOutput= or
@@ -687,7 +687,7 @@
User= setting. If
not set, no PAM session will be opened
for the executed processes. See
- pam8
+ pam8
for details.
@@ -698,7 +698,7 @@
capabilities to include in the
capability bounding set for the
executed process. See
- capabilities7
+ capabilities7
for details. Takes a whitespace-separated
list of capability names as read by
cap_from_name3,
@@ -739,7 +739,7 @@
SecureBits=Controls the secure
bits set for the executed process. See
- capabilities7
+ capabilities7
for details. Takes a list of strings:
,
,
@@ -757,14 +757,14 @@
Capabilities=Controls the
- capabilities7
+ capabilities7
set for the executed process. Take a
capability string describing the
effective, permitted and inherited
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=
@@ -777,8 +777,8 @@
ReadOnlyDirectories=InaccessibleDirectories=
- Sets up a new
- file system namespace for executed
+ Sets up a new file
+ system namespace for executed
processes. These options may be used
to limit access a process might have
to the main file system
@@ -799,16 +799,14 @@
processes inside the namespace. Note
that restricting access with these
options does not extend to submounts
- of a directory. You must list
- submounts separately in these settings
- to ensure the same limited
- access. These options may be specified
+ of a directory that are created later
+ on. These options may be specified
more than once in which case all
directories listed will have limited
access from within the namespace. If
the empty string is assigned to this
- option, the specific list is reset, and
- all prior assignments have no
+ option, the specific list is reset,
+ and all prior assignments have no
effect.Paths in
ReadOnlyDirectories=
@@ -934,6 +932,67 @@
accessible).
+
+ ProtectSystem=
+
+ Takes a boolean
+ argument or
+ full. If true,
+ mounts the /usr
+ directory read-only for processes
+ invoked by this unit. If set to
+ full, the
+ /etc directory 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 +1027,8 @@
namespace related options
(PrivateTmp=,
PrivateDevices=,
+ ProtectSystem=,
+ ProtectHome=,
ReadOnlyDirectories=,
InaccessibleDirectories=
and
@@ -1275,7 +1336,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
@@ -1411,7 +1472,7 @@
or
StandardError=tty).
See
- termcap5.
+ termcap5.
@@ -1427,7 +1488,7 @@
systemd.setenv= (see
systemd1). Additional
variables may also be set through PAM,
- cf. pam_env8.
+ cf. pam_env8.
@@ -1445,7 +1506,7 @@
systemd.resource-control5,
systemd.directives7,
tmpfiles.d5,
- exec3
+ exec3