X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=man%2Fsystemd.exec.html;h=41aa03238c676369f5c1a9be99e405238409fabe;hb=14228c0ddf1fe80e2ed0193f0cd1cdb06e5db522;hp=d7fb2cbfd541d17f409c8d7736c0c00acaf010ed;hpb=663996b3bb3cdaa81ac830674fdda00e28a2485b;p=systemd.git diff --git a/man/systemd.exec.html b/man/systemd.exec.html index d7fb2cbfd..41aa03238 100644 --- a/man/systemd.exec.html +++ b/man/systemd.exec.html @@ -19,11 +19,11 @@ Directives · Python · libudev · - gudev systemd 204
systemd.exec â Execution environment configuration
,
+ gudev systemd 208service
.service
systemd.exec â Execution environment configuration
,
service
.service
,
socket
.socket
,
- mount
.mountswap
.swap
Unit configuration files for services, sockets,
- mount points and swap devices share a subset of
+ swap
.swap
Unit configuration files for services, sockets, + mount points, and swap devices share a subset of configuration options which define the execution environment of spawned processes.
This man page lists the configuration options shared by these four unit types. See @@ -32,17 +32,17 @@ files, and systemd.service(5), systemd.socket(5), - systemd.swap(5) + systemd.swap(5), and systemd.mount(5) for more information on the specific unit configuration files. The execution specific configuration options are configured in the [Service], [Socket], [Mount], or [Swap] sections, depending on the unit - type.
WorkingDirectory=
¶Takes an absolute + type.
WorkingDirectory=
¶Takes an absolute
directory path. Sets the working
directory for executed processes. If
- not set defaults to the root directory
+ not set, defaults to the root directory
when systemd is running as a system
instance and the respective user's
home directory if run as
@@ -51,7 +51,7 @@
directory for executed processes, with
the
chroot(2)
- system call. If this is used it must
+ system call. If this is used, it must
be ensured that the process and all
its auxiliary files are available in
the chroot()
@@ -62,7 +62,7 @@
set, the default group of the user is
chosen.
SupplementaryGroups=
¶Sets the supplementary Unix groups the processes are executed - as. This takes a space separated list + as. This takes a space-separated list of group names or IDs. This option may be specified more than once in which case all listed groups are set as @@ -87,7 +87,7 @@ between -1000 (to disable OOM killing for this process) and 1000 (to make killing of this process under memory - pressure very likely). See proc.txt + pressure very likely). See proc.txt for details.
IOSchedulingClass=
¶Sets the IO scheduling class for executed processes. Takes an integer between 0 and 3 or one of the @@ -124,7 +124,7 @@ See sched_setscheduler(2) for details.
CPUSchedulingResetOnFork=
¶Takes a boolean - argument. If true elevated CPU + argument. If true, elevated CPU scheduling priorities and policies will be reset when the executed processes fork, and can hence not leak @@ -137,7 +137,7 @@ be specified more than once in which case the specificed CPU affinity masks are merged. If the empty string is - assigned the mask is reset, all + assigned, the mask is reset, all assignments prior to this will have no effect. See sched_setaffinity(2) @@ -153,21 +153,22 @@ option may be specified more than once in which case all listed variables will be set. If the same variable is - set twice the later setting will + set twice, the later setting will override the earlier setting. If the empty string is assigned to this - option the list of environment + option, the list of environment variables is reset, all prior assignments have no effect. Variable expansion is not performed - inside the strings, and $ has no special - meaning. + inside the strings, however, specifier + expansion is possible. The $ character has + no special meaning. If you need to assign a value containing spaces to a variable, use double quotes (") for the assignment.
Example:
Environment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"
- gives three variables VAR1
,
- VAR2
, VAR3
.
+ gives three variables "VAR1
",
+ "VAR2
", "VAR3
".
See
environ(7)
@@ -175,7 +176,7 @@
Environment=
but
reads the environment variables from a
text file. The text file should
- contain new-line separated variable
+ contain new-line-separated variable
assignments. Empty lines and lines
starting with ; or # will be ignored,
which may be used for commenting. A line
@@ -185,24 +186,25 @@
and trailing whitespace from the values
of assignments, unless you use
double quotes (").
The argument passed should be an - absolute file name or wildcard + absolute filename or wildcard expression, optionally prefixed with - "-", which indicates that if the file - does not exist it won't be read and no - error or warning message is logged. - This option may be specified more than - once in which case all specified files - are read. If the empty string is - assigned to this option the list of - file to read is reset, all prior - assignments have no effect.
The files listed with this
+ "-
", which indicates
+ that if the file does not exist, it
+ will not be read and no error or warning
+ message is logged. This option may be
+ specified more than once in which case
+ all specified files are read. If the
+ empty string is assigned to this
+ option, the list of file to read is
+ reset, all prior assignments have no
+ effect.
The files listed with this
directive will be read shortly before
the process is executed. 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
+ these files, the files will be read in
the order they are specified and the
later setting will override the
earlier setting.
StandardInput=
¶Controls where file
@@ -213,19 +215,19 @@
tty-force
,
tty-fail
or
socket
. If
- null
is selected
+ null
is selected,
standard input will be connected to
/dev/null
,
i.e. all read attempts by the process
will result in immediate EOF. If
- tty
is selected
+ tty
is selected,
standard input is connected to a TTY
(as configured by
TTYPath=
, see
below) and the executed process
becomes the controlling process of the
terminal. If the terminal is already
- being controlled by another process the
+ being controlled by another process, the
executed process waits until the current
controlling process releases the
terminal.
@@ -247,7 +249,7 @@
file (see
systemd.socket(5)
for details) specifies a single socket
- only. If this option is set standard
+ only. If this option is set, standard
input will be connected to the socket
the service was activated from, which
is primarily useful for compatibility
@@ -268,19 +270,19 @@
kmsg+console
,
journal+console
or
socket
. If set to
- inherit
the file
+ inherit
, the file
descriptor of standard input is
duplicated for standard output. If set
- to null
standard
+ to null
, standard
output will be connected to
/dev/null
,
i.e. everything written to it will be
- lost. If set to tty
+ lost. If set to tty
,
standard output will be connected to a
tty (as configured via
TTYPath=
, see
below). If the TTY is used for output
- only the executed process will not
+ only, the executed process will not
become the controlling process of the
terminal, and will not fail or wait
for other processes to release the
@@ -338,23 +340,23 @@
device specified with
TTYPath=
before and
after execution. Defaults to
- no
.
TTYVHangup=
¶Disconnect all clients
+ "no
".
TTYVHangup=
¶Disconnect all clients
which have opened the terminal device
specified with
TTYPath=
before and after execution. Defaults
to
- no
.
TTYVTDisallocate=
¶If the terminal
+ "no
".
TTYVTDisallocate=
¶If the terminal
device specified with
TTYPath=
is a
- virtual console terminal try to
+ virtual console terminal, try to
deallocate the TTY before and after
execution. This ensures that the
screen and scrollback buffer is
cleared. Defaults to
- no
.
SyslogIdentifier=
¶Sets the process name
+ "no
".
SyslogIdentifier=
¶Sets the process name
to prefix log lines sent to syslog or
- the kernel log buffer with. If not set
+ the kernel log buffer with. If not set,
defaults to the process name of the
executed process. This option is only
useful when
@@ -455,17 +457,17 @@
infinity
to
configure no limit on a specific
resource.
PAMName=
¶Sets the PAM service
- name to set up a session as. If set
+ name to set up a session as. If set,
the executed process will be
registered as a PAM session under the
specified service name. This is only
useful in conjunction with the
User=
setting. If
- not set no PAM session will be opened
+ not set, no PAM session will be opened
for the executed processes. See
pam(8)
for details.
TCPWrapName=
¶If this is a
- socket-activated service this sets the
+ socket-activated service, this sets the
tcpwrap service name to check the
permission for the current connection
with. This is only useful in
@@ -475,7 +477,7 @@
socket types (e.g. datagram/UDP) and
on processes unrelated to socket-based
activation. If the tcpwrap
- verification fails daemon start-up
+ verification fails, daemon start-up
will fail and the connection is
terminated. See
tcpd(8)
@@ -489,17 +491,16 @@
capability bounding set for the
executed process. See
capabilities(7)
- for details. Takes a whitespace
- separated list of capability names as
- read by
+ for details. Takes a whitespace-separated
+ list of capability names as read by
cap_from_name(3),
- e.g. CAP_SYS_ADMIN
- CAP_DAC_OVERRIDE
- CAP_SYS_PTRACE
.
+ e.g. CAP_SYS_ADMIN
,
+ CAP_DAC_OVERRIDE
,
+ CAP_SYS_PTRACE
.
Capabilities listed will be included
in the bounding set, all others are
removed. If the list of capabilities
- is prefixed with ~
+ is prefixed with "~
",
all but the listed capabilities will
be included, the effect of the
assignment inverted. Note that this
@@ -508,7 +509,7 @@
permitted and inheritable capability
sets, on top of what
Capabilities=
- does. If this option is not used the
+ does. If this option is not used, the
capability bounding set is not
modified on process execution, hence
no limits on the capabilities of the
@@ -516,11 +517,11 @@
appear more than once in which case
the bounding sets are merged. If the
empty string is assigned to this
- option the bounding set is reset to
+ option, the bounding set is reset to
the empty capability set, and all
prior settings have no effect. If set
- to ~
(without any
- further argument) the bounding set is
+ to "~
" (without any
+ further argument), the bounding set is
reset to the full set of available
capabilities, also undoing any
previous settings.
SecureBits=
¶Controls the secure @@ -536,7 +537,7 @@ option may appear more than once in which case the secure bits are ORed. If the empty string is assigned - to this option the bits are reset to + to this option, the bits are reset to 0.
Capabilities=
¶Controls the
capabilities(7)
set for the executed process. Take a
@@ -550,214 +551,11 @@
that
CapabilityBoundingSet=
is probably the much more useful
- setting.
ControlGroup=
¶Controls the control
- groups the executed processes shall be
- made members of. Takes a
- space-separated list of cgroup
- identifiers. A cgroup identifier is
- formatted like
- cpu:/foo/bar
,
- where "cpu" indicates the kernel
- control group controller used, and
- /foo/bar
is the
- control group path. The controller
- name and ":" may be omitted in which
- case the named systemd control group
- hierarchy is implied. Alternatively,
- the path and ":" may be omitted, in
- which case the default control group
- path for this unit is implied.
This option may be used to place
- executed processes in arbitrary groups
- in arbitrary hierarchies -- which may
- then be externally configured with
- additional execution limits. By
- default systemd will place all
- executed processes in separate
- per-unit control groups (named after
- the unit) in the systemd named
- hierarchy. This option is primarily
- intended to place executed processes
- in specific paths in specific kernel
- controller hierarchies. It is not
- recommended to manipulate the service
- control group path in the private
- systemd named hierarchy
- (i.e. name=systemd
),
- and doing this might result in
- undefined behaviour. For details about
- control groups see cgroups.txt.
This option may appear more than - once, in which case the list of - control group assignments is - merged. If the same hierarchy gets two - different paths assigned only the - later setting will take effect. If the - empty string is assigned to this - option the list of control group - assignments is reset, all previous - assignments will have no - effect.
Note that the list of control
- group assignments of a unit is
- extended implicitly based on the
- settings of
- DefaultControllers=
- of
- systemd-system.conf(5),
- but a unit's
- ControlGroup=
- setting for a specific controller
- takes precedence.
ControlGroupModify=
¶Takes a boolean
- argument. If true, the control groups
- created for this unit will be owned by
- the user specified with
- User=
(and the
- appropriate group), and he/she can create
- subgroups as well as add processes to
- the group.
ControlGroupPersistent=
¶Takes a boolean - argument. If true, the control groups - created for this unit will be marked - to be persistent, i.e. systemd will - not remove them when stopping the - unit. The default is false, meaning - that the control groups will be - removed when the unit is stopped. For - details about the semantics of this - logic see PaxControlGroups.
ControlGroupAttribute=
¶Set a specific control
- group attribute for executed
- processes, and (if needed) add the
- executed processes to a cgroup in the
- hierarchy of the controller the
- attribute belongs to. Takes two
- space-separated arguments: the
- attribute name (syntax is
- cpu.shares
where
- cpu
refers to a
- specific controller and
- shares
to the
- attribute name), and the attribute
- value. Example:
- ControlGroupAttribute=cpu.shares
- 512
. If this option is used
- for an attribute that belongs to a
- kernel controller hierarchy the unit
- is not already configured to be added
- to (for example via the
- ControlGroup=
- option) then the unit will be added to
- the controller and the default unit
- cgroup path is implied. Thus, using
- ControlGroupAttribute=
- is in most cases sufficient to make
- use of control group enforcements,
- explicit
- ControlGroup=
are
- only necessary in case the implied
- default control group path for a
- service is not desirable. For details
- about control group attributes see
- cgroups.txt. This
- option may appear more than once, in
- order to set multiple control group
- attributes. If this option is used
- multiple times for the same cgroup
- attribute only the later setting takes
- effect. If the empty string is
- assigned to this option the list of
- attributes is reset, all previous
- cgroup attribute settings have no
- effect, including those done with
- CPUShares=
,
- MemoryLimit=
,
- MemorySoftLimit
,
- DeviceAllow=
,
- DeviceDeny=
,
- BlockIOWeight=
,
- BlockIOReadBandwidth=
,
- BlockIOWriteBandwidth=
.
-
Assign the specified
- overall CPU time shares to the
- processes executed. Takes an integer
- value. This controls the
- cpu.shares
control
- group attribute, which defaults to
- 1024. For details about this control
- group attribute see sched-design-CFS.txt.
MemoryLimit=
, MemorySoftLimit=
¶Limit the overall memory usage
- of the executed processes to a certain
- size. Takes a memory size in bytes. If
- the value is suffixed with K, M, G or
- T the specified memory size is parsed
- as Kilobytes, Megabytes, Gigabytes,
- or Terabytes (to the base
- 1024), respectively. This controls the
- memory.limit_in_bytes
- and
- memory.soft_limit_in_bytes
- control group attributes. For details
- about these control group attributes
- see memory.txt.
DeviceAllow=
, DeviceDeny=
¶Control access to
- specific device nodes by the executed processes. Takes two
- space separated strings: a device node
- path (such as
- /dev/null
)
- followed by a combination of r, w, m
- to control reading, writing, or
- creating of the specific device node
- by the unit, respectively. This controls the
- devices.allow
- and
- devices.deny
- control group attributes. For details
- about these control group attributes
- see devices.txt.
BlockIOWeight=
¶Set the default or
- per-device overall block IO weight
- value for the executed
- processes. Takes either a single
- weight value (between 10 and 1000) to
- set the default block IO weight, or a
- space separated pair of a file path
- and a weight value to specify the
- device specific weight value (Example:
- "/dev/sda 500"). The file path may be
- specified as path to a block device
- node or as any other file in which
- case the backing block device of the
- file system of the file is
- determined. This controls the
- blkio.weight
and
- blkio.weight_device
- control group attributes, which
- default to 1000. Use this option
- multiple times to set weights for
- multiple devices. For details about
- these control group attributes see
- blkio-controller.txt.
BlockIOReadBandwidth=
, BlockIOWriteBandwidth=
¶Set the per-device
- overall block IO bandwidth limit for
- the executed processes. Takes a space
- separated pair of a file path and a
- bandwidth value (in bytes per second)
- to specify the device specific
- bandwidth. The file path may be
- specified as path to a block device
- node or as any other file in which
- case the backing block device of the
- file system of the file is determined.
- If the bandwidth is suffixed with K, M,
- G, or T the specified bandwidth is
- parsed as Kilobytes, Megabytes,
- Gigabytes, or Terabytes, respectively (Example:
- "/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0
- 5M"). This controls the
- blkio.read_bps_device
- and
- blkio.write_bps_device
- control group attributes. Use this
- option multiple times to set bandwidth
- limits for multiple devices. For
- details about these control group
- attributes see blkio-controller.txt.
ReadWriteDirectories=
, ReadOnlyDirectories=
, InaccessibleDirectories=
¶Sets up a new - file-system name space for executed + setting.
ReadWriteDirectories=
, ReadOnlyDirectories=
, InaccessibleDirectories=
¶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 + to the main file system hierarchy. Each setting takes a space-separated list of absolute directory paths. Directories listed in @@ -783,10 +581,17 @@ 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 + option, the specific list is reset, and all prior assignments have no - effect.
PrivateTmp=
¶Takes a boolean - argument. If true sets up a new file + effect.
Paths in
+ ReadOnlyDirectories=
+ and
+ InaccessibleDirectories=
+ may be prefixed with
+ "-
", in which case
+ they will be ignored when they do not
+ exist.
PrivateTmp=
¶Takes a boolean
+ argument. If true, sets up a new file
system namespace for the executed
processes and mounts private
/tmp
and
@@ -803,11 +608,11 @@
by service will be removed after service
is stopped. Defaults to
false.
PrivateNetwork=
¶Takes a boolean
- argument. If true sets up a new
+ argument. If true, sets up a new
network namespace for the executed
processes and configures only the
loopback network device
- lo
inside it. No
+ "lo
" inside it. No
other network devices will be
available to the executed process.
This is useful to securely turn off
@@ -833,19 +638,19 @@
entries must be created and cleared
before and after execution. If the
configured string is longer than four
- characters it is truncated and the
+ characters, it is truncated and the
terminal four characters are
used. This setting interprets %I style
string replacements. This setting is
unset by default, i.e. no utmp/wtmp
entries are created or cleaned up for
this service.
IgnoreSIGPIPE=
¶Takes a boolean
- argument. If true causes SIGPIPE to be
+ argument. If true, causes SIGPIPE
to be
ignored in the executed
- process. Defaults to true, since
- SIGPIPE generally is useful only in
+ process. Defaults to true because
+ SIGPIPE
generally is useful only in
shell pipelines.
NoNewPrivileges=
¶Takes a boolean - argument. If true ensures that the + argument. If true, ensures that the service process and all its children can never gain new privileges. This option is more powerful than the respective @@ -854,19 +659,20 @@ kind. This is the simplest, most effective way to ensure that a process and its children can never elevate - privileges again.
SystemCallFilter=
¶Takes a space - separated list of system call - names. If this setting is used all + privileges again.
SystemCallFilter=
¶Takes a space-separated
+ list of system call
+ names. If this setting is used, all
system calls executed by the unit
process except for the listed ones
will result in immediate process
- termination with the SIGSYS signal
+ termination with the
+ SIGSYS
signal
(whitelisting). If the first character
- of the list is ~
+ of the list is "~
",
the effect is inverted: only the
listed system calls will result in
immediate process termination
- (blacklisting). If this option is used
+ (blacklisting). If this option is used,
NoNewPrivileges=yes
is implied. This feature makes use of
the Secure Computing Mode 2 interfaces
@@ -878,14 +684,70 @@
sigreturn
,
exit_group
,
exit
system calls
- are implicitly whitelisted and don't
+ are implicitly whitelisted and do not
need to be listed explicitly. This
option may be specified more than once
in which case the filter masks are
merged. If the empty string is
- assigned the filter is reset, all
+ assigned, the filter is reset, all
prior assignments will have no
- effect.
Processes started by the system are executed in + a clean environment in which select variables + listed below are set. System processes started by systemd + do not inherit variables from PID 1, but processes + started by user systemd instances inherit all + environment variables from the user systemd instance. +
$PATH
¶Colon-separated list
+ of directiories to use when launching
+ executables. Systemd uses a fixed
+ value of
+ /usr/local/sbin
:/usr/local/bin
:/usr/sbin
:/usr/bin
:/sbin
:/bin
.
+
$LANG
¶Locale. Can be set in + locale.conf(5) + or on the kernel command line (see + systemd(1) + and + kernel-command-line(7)). +
$USER
, $HOME
¶User name and home
+ directory. Set for the units which
+ have User=
set,
+ which includes user
+ systemd instances.
+ See
+ passwd(5).
+
$XDG_RUNTIME_DIR
¶The directory for volatile + state. Set for the user systemd + instance, and also in user sessions. + See + pam_systemd(8). +
$XDG_SESSION_ID
, $XDG_SEAT
, $XDG_VTNR
¶The identifier of the
+ session, and the seat name, and
+ virtual terminal of the session. Set
+ by
+ pam_systemd(8)
+ for login sessions.
+ $XDG_SEAT
and
+ $XDG_VTNR
will be
+ only set when attached to a seat and a
+ tty.
$MANAGERPID
¶The PID of the user + systemd instance, + set for processes spawned by it. +
$LISTEN_FDS
, $LISTEN_PID
¶Information about file + descriptors passed to a service for + socket activation. See + sd_listen_fds(3). +
Additional variables may be configured by the
+ following means: for processes spawned in specific
+ units, use the Environment=
and
+ EnvironmentFile=
options above; to
+ specify variables globally, use
+ DefaultEnvironment=
(see
+ systemd-system.conf(5))
+ or the kernel option
+ systemd.setenv=
(see
+ systemd(1)). Additional
+ variables may also be set through PAM,
+ c.f. pam_env(8).
systemd(1), systemctl(8), journalctl(8), @@ -895,5 +757,7 @@ systemd.swap(5), systemd.mount(5), systemd.kill(5), - systemd.directives(7) + systemd.resource-control(5), + systemd.directives(7), + exec(3)