X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.exec.xml;h=5d39bd1a142f49c7e6e87a600eb5e6d673816bd8;hb=05a2f6fefedd7254fd799502191d025d2908cf74;hp=9224f1ef3d5e38afcb6e2d83b4fc08f3a1f24244;hpb=f513e420c8b1a1d4c13092cd378f048b69793497;p=elogind.git
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 9224f1ef3..5d39bd1a1 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -340,9 +340,14 @@
The files listed with this
directive will be read shortly before
- the process is executed. Settings from
- these files override settings made
- with
+ the process is executed (more
+ specifically, this means after all
+ processes from a previous unit state
+ terminated. This means you can
+ generate these files in one unit
+ state, and read it with this option in
+ the next). Settings from these files
+ override settings made with
Environment=. If
the same variable is set twice from
these files, the files will be read in
@@ -686,31 +691,6 @@
for details.
-
- TCPWrapName=
- If this is a
- socket-activated service, this sets the
- tcpwrap service name to check the
- permission for the current connection
- with. This is only useful in
- conjunction with socket-activated
- services, and stream sockets (TCP) in
- particular. It has no effect on other
- socket types (e.g. datagram/UDP) and
- on processes unrelated to socket-based
- activation. If the tcpwrap
- verification fails, daemon start-up
- will fail and the connection is
- terminated. See
- tcpd8
- for details. Note that this option may
- be used to do access control checks
- only. Shell commands and commands
- described in
- hosts_options5
- are not supported.
-
-
CapabilityBoundingSet=
@@ -837,7 +817,15 @@
may be prefixed with
-, in which case
they will be ignored when they do not
- exist.
+ exist. Note that using this
+ setting will disconnect propagation of
+ mounts from the service to the host
+ (propagation in the opposite direction
+ continues to work). This means that
+ this setting may not be used for
+ services which shall be able to
+ install mount points in the main mount
+ namespace.
@@ -857,18 +845,61 @@
processes via
/tmp or
/var/tmp
- impossible. All temporary data created
- by service will be removed after
- the service is stopped. Defaults to
- false. Note that it is possible to run
- two or more units within the same
- private /tmp and
+ impossible. If this is enabled all
+ temporary files created by a service
+ in these directories will be removed
+ after the service is stopped. Defaults
+ to false. It is possible to run two or
+ more units within the same private
+ /tmp and
/var/tmp
namespace by using the
JoinsNamespaceOf=
directive, see
systemd.unit5
- for details.
+ for details. Note that using this
+ setting will disconnect propagation of
+ mounts from the service to the host
+ (propagation in the opposite direction
+ continues to work). This means that
+ this setting may not be used for
+ services which shall be able to install
+ mount points in the main mount
+ namespace.
+
+
+
+ PrivateDevices=
+
+ Takes a boolean
+ argument. If true, sets up a new /dev
+ namespace for the executed processes
+ and only adds API pseudo devices such
+ as /dev/null,
+ /dev/zero or
+ /dev/random (as
+ well as the pseudo TTY subsystem) to
+ it, but no physical devices such as
+ /dev/sda. This is
+ useful to securely turn off physical
+ device access by the executed
+ process. Defaults to false. Enabling
+ this option will also remove
+ CAP_MKNOD from
+ the capability bounding set for the
+ unit (see above), and set
+ DevicePolicy=closed
+ (see
+ systemd.resource-control5
+ for details). Note that using this
+ setting will disconnect propagation of
+ mounts from the service to the host
+ (propagation in the opposite direction
+ continues to work). This means that
+ this setting may not be used for
+ services which shall be able to
+ install mount points in the main mount
+ namespace.
@@ -884,32 +915,23 @@
available to the executed process.
This is useful to securely turn off
network access by the executed
- process. Defaults to false. Note that
- it is possible to run two or more
- units within the same private network
+ process. Defaults to false. It is
+ possible to run two or more units
+ within the same private network
namespace by using the
JoinsNamespaceOf=
directive, see
systemd.unit5
- for details.
-
-
-
- PrivateDevices=
-
- Takes a boolean
- argument. If true, sets up a new /dev
- namespace for the executed processes
- and only adds API pseudo devices such
- as /dev/null,
- /dev/zero or
- /dev/random to
- it, but no physical devices such as
- /dev/sda. This is
- useful to securely turn off physical
- device access by the executed
- process. Defaults to
- false.
+ for details. Note that this option
+ will disconnect all socket families
+ from the host, this includes
+ AF_NETLINK and AF_UNIX. The latter has
+ the effect that AF_UNIX sockets in the
+ abstract socket namespace will become
+ unavailable to the processes (however,
+ those located in the file system will
+ continue to be
+ accessible).
@@ -920,13 +942,43 @@
,
or
, which
- control whether the file system
- namespace set up for this unit's
- processes will receive or propagate
- new mounts. See
+ control whether mounts in the file
+ system namespace set up for this
+ unit's processes will receive or
+ propagate mounts or unmounts. See
mount2
- for details. Default to
- .
+ for details. Defaults to
+ . Use
+ to ensure that
+ mounts and unmounts are propagated
+ from the host to the container and
+ vice versa. Use
+ to run processes so that none of their
+ mounts and unmounts will propagate to
+ the host. Use
+ to also ensure that no mounts and
+ unmounts from the host will propagate
+ into the unit processes'
+ namespace. Note that
+ means that file
+ systems mounted on the host might stay
+ mounted continously in the unit's
+ namespace, and thus keep the device
+ busy. Note that the file system
+ namespace related options
+ (PrivateTmp=,
+ PrivateDevices=,
+ ReadOnlyDirectories=,
+ InaccessibleDirectories=
+ and
+ ReadWriteDirectories=)
+ require that mount and unmount
+ propagation from the unit's file
+ system namespace is disabled, and
+ hence downgrade
+ to
+ .
+
@@ -1195,6 +1247,46 @@
kernel.
+
+ RuntimeDirectory=
+ RuntimeDirectoryMode=
+
+ Takes a list of
+ 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
+ stopped. The directories will have the
+ access mode specified in
+ RuntimeDirectoryMode=,
+ and will be owned by the user and
+ group specified in
+ User= and
+ Group=. Use this to
+ manage one or more runtime directories
+ of the unit and bind their lifetime to
+ the daemon runtime. The specified
+ directory names must be relative, and
+ may not include a
+ /, i.e. must refer
+ to simple directories to create or
+ remove. This is particularly useful
+ for unpriviliges daemons that cannot
+ create runtime directories in
+ /run due to lack
+ of privileges, and to make sure the
+ runtime directory is cleaned up
+ automatically after use. For runtime
+ directories that require more complex
+ or different configuration or lifetime
+ guarantees, please consider using
+ tmpfiles.d5.
+
+
@@ -1352,6 +1444,7 @@
systemd.kill5,
systemd.resource-control5,
systemd.directives7,
+ tmpfiles.d5,
exec3