CPUAccounting¶

CPUWeight¶

While "StartupCPUWeight" only applies to the startup phase of the system, "CPUWeight" applies to normal runtime of the system, and if the former is not set also to the startup phase. Using "StartupCPUWeight" allows prioritizing specific services at boot-up differently than during normal runtime.

Implies "CPUAccounting=true".

These settings replace "CPUShares" and "StartupCPUShares". Optional. Type integer. upstream_default: '100'.

StartupCPUWeight¶

While "StartupCPUWeight" only applies to the startup phase of the system, "CPUWeight" applies to normal runtime of the system, and if the former is not set also to the startup phase. Using "StartupCPUWeight" allows prioritizing specific services at boot-up differently than during normal runtime.

Implies "CPUAccounting=true".

These settings replace "CPUShares" and "StartupCPUShares". Optional. Type integer. upstream_default: '100'.

CPUQuota¶

Example: "CPUQuota=20%" ensures that the executed processes will never get more than 20% CPU time on one CPU.

Implies "CPUAccounting=true". Optional. Type uniline.

MemoryAccounting¶

MemoryLow¶

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 (with the base 1024), respectively. Alternatively, a percentage value may be specified, which is taken relative to the installed physical memory on the system. This controls the "memory.low" control group attribute. For details about this control group attribute, see cgroup-v2.txt.

Implies "MemoryAccounting=true".

This setting is supported only if the unified control group hierarchy is used and disables "MemoryLimit". Optional. Type uniline.

MemoryHigh¶

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 (with the base 1024), respectively. Alternatively, a percentage value may be specified, which is taken relative to the installed physical memory on the system. If assigned the special value "infinity", no memory limit is applied. This controls the "memory.high" control group attribute. For details about this control group attribute, see cgroup-v2.txt.

Implies "MemoryAccounting=true".

This setting is supported only if the unified control group hierarchy is used and disables "MemoryLimit". Optional. Type uniline.

MemoryMax¶

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 (with the base 1024), respectively. Alternatively, a percentage value may be specified, which is taken relative to the installed physical memory on the system. If assigned the special value "infinity", no memory limit is applied. This controls the "memory.max" control group attribute. For details about this control group attribute, see cgroup-v2.txt.

Implies "MemoryAccounting=true".

This setting replaces "MemoryLimit". Optional. Type uniline.

MemorySwapMax¶

Takes a swap size in bytes. If the value is suffixed with K, M, G or T, the specified swap size is parsed as Kilobytes, Megabytes, Gigabytes, or Terabytes (with the base 1024), respectively. If assigned the special value "infinity", no swap limit is applied. This controls the "memory.swap.max" control group attribute. For details about this control group attribute, see cgroup-v2.txt.

Implies "MemoryAccounting=true".

This setting is supported only if the unified control group hierarchy is used and disables "MemoryLimit". Optional. Type uniline.

TasksAccounting¶

TasksMax¶

Implies "TasksAccounting=true". The system default for this setting may be controlled with "DefaultTasksMax" in systemd-system.conf(5). Optional. Type uniline.

IOAccounting¶

This setting replaces "BlockIOAccounting" and disables settings prefixed with "BlockIO" or "StartupBlockIO". Optional. Type boolean.

IOWeight¶

While "StartupIOWeight" only applies to the startup phase of the system, "IOWeight" applies to the later runtime of the system, and if the former is not set also to the startup phase. This allows prioritizing specific services at boot-up differently than during runtime.

Implies "IOAccounting=true".

These settings replace "BlockIOWeight" and "StartupBlockIOWeight" and disable settings prefixed with "BlockIO" or "StartupBlockIO". Optional. Type uniline.

StartupIOWeight¶

While "StartupIOWeight" only applies to the startup phase of the system, "IOWeight" applies to the later runtime of the system, and if the former is not set also to the startup phase. This allows prioritizing specific services at boot-up differently than during runtime.

Implies "IOAccounting=true".

These settings replace "BlockIOWeight" and "StartupBlockIOWeight" and disable settings prefixed with "BlockIO" or "StartupBlockIO". Optional. Type uniline.

IODeviceWeight¶

Implies "IOAccounting=true".

This setting replaces "BlockIODeviceWeight" and disables settings prefixed with "BlockIO" or "StartupBlockIO". Optional. Type uniline.

IOReadBandwidthMax¶

Implies "IOAccounting=true".

These settings replace "BlockIOReadBandwidth" and "BlockIOWriteBandwidth" and disable settings prefixed with "BlockIO" or "StartupBlockIO". Optional. Type uniline.

IOWriteBandwidthMax¶

Implies "IOAccounting=true".

These settings replace "BlockIOReadBandwidth" and "BlockIOWriteBandwidth" and disable settings prefixed with "BlockIO" or "StartupBlockIO". Optional. Type uniline.

IOReadIOPSMax¶

Implies "IOAccounting=true".

These settings are supported only if the unified control group hierarchy is used and disable settings prefixed with "BlockIO" or "StartupBlockIO". Optional. Type uniline.

IOWriteIOPSMax¶

Implies "IOAccounting=true".

These settings are supported only if the unified control group hierarchy is used and disable settings prefixed with "BlockIO" or "StartupBlockIO". Optional. Type uniline.

DeviceAllow¶

The device node specifier is either a path to a device node in the file system, starting with /dev/, or a string starting with either "char-" or "block-" followed by a device group name, as listed in /proc/devices. The latter is useful to whitelist all current and future devices belonging to a specific device group at once. The device group is matched according to file name globbing rules, you may hence use the "*" and "?" wildcards. Examples: /dev/sda5 is a path to a device node, referring to an ATA or SCSI block device. "char-pts" and "char-alsa" are specifiers for all pseudo TTYs and all ALSA sound devices, respectively. "char-cpu/*" is a specifier matching all CPU related device groups. Optional. Type uniline.

DevicePolicy¶

Slice¶

This option may be used to arrange systemd units in a hierarchy of slices each of which might have resource settings applied.

For units of type slice, the only accepted value for this setting is the parent slice. Since the name of a slice unit implies the parent slice, it is hence redundant to ever set this parameter directly for slice units.

Special care should be taken when relying on the default slice assignment in templated service units that have "DefaultDependencies=no" set, see systemd.service(5), section "Automatic Dependencies" for details. Optional. Type uniline.

Delegate¶

CPUShares¶

While "StartupCPUShares" only applies to the startup phase of the system, "CPUShares" applies to normal runtime of the system, and if the former is not set also to the startup phase. Using "StartupCPUShares" allows prioritizing specific services at boot-up differently than during normal runtime.

Implies "CPUAccounting=true".

These settings are deprecated. Use "CPUWeight" and "StartupCPUWeight" instead. Optional. Type integer. upstream_default: '1024'.

StartupCPUShares¶

While "StartupCPUShares" only applies to the startup phase of the system, "CPUShares" applies to normal runtime of the system, and if the former is not set also to the startup phase. Using "StartupCPUShares" allows prioritizing specific services at boot-up differently than during normal runtime.

Implies "CPUAccounting=true".

These settings are deprecated. Use "CPUWeight" and "StartupCPUWeight" instead. Optional. Type integer. upstream_default: '1024'.

MemoryLimit¶

Implies "MemoryAccounting=true".

This setting is deprecated. Use "MemoryMax" instead. Optional. Type uniline.

BlockIOAccounting¶

This setting is deprecated. Use "IOAccounting" instead. Optional. Type boolean.

BlockIOWeight¶

While "StartupBlockIOWeight" only applies to the startup phase of the system, "BlockIOWeight" applies to the later runtime of the system, and if the former is not set also to the startup phase. This allows prioritizing specific services at boot-up differently than during runtime.

Implies "BlockIOAccounting=true".

These settings are deprecated. Use "IOWeight" and "StartupIOWeight" instead. Optional. Type uniline.

StartupBlockIOWeight¶

While "StartupBlockIOWeight" only applies to the startup phase of the system, "BlockIOWeight" applies to the later runtime of the system, and if the former is not set also to the startup phase. This allows prioritizing specific services at boot-up differently than during runtime.

Implies "BlockIOAccounting=true".

These settings are deprecated. Use "IOWeight" and "StartupIOWeight" instead. Optional. Type uniline.

BlockIODeviceWeight¶

Implies "BlockIOAccounting=true".

This setting is deprecated. Use "IODeviceWeight" instead. Optional. Type uniline.

BlockIOReadBandwidth¶

Implies "BlockIOAccounting=true".

These settings are deprecated. Use "IOReadBandwidthMax" and "IOWriteBandwidthMax" instead. Optional. Type uniline.

BlockIOWriteBandwidth¶

Implies "BlockIOAccounting=true".

These settings are deprecated. Use "IOReadBandwidthMax" and "IOWriteBandwidthMax" instead. Optional. Type uniline.

WorkingDirectory¶

RootDirectory¶

The "PrivateUsers" setting is particularly useful in conjunction with "RootDirectory". For details, see below. Optional. Type uniline.

User¶

Group¶

DynamicUser¶

SupplementaryGroups¶

RemoveIPC¶

Nice¶

OOMScoreAdjust¶

IOSchedulingClass¶

IOSchedulingPriority¶

CPUSchedulingPolicy¶

CPUSchedulingPriority¶

CPUSchedulingResetOnFork¶

CPUAffinity¶

UMask¶

Environment¶

Example:

    Environment="VAR1=word1 word2" VAR2=word3 "VAR3=$word 5 6"

gives three variables "VAR1", "VAR2", "VAR3" with the values "word1 word2", "word3", "$word 5 6".

See environ(7) for details about environment variables. Optional. Type list of uniline.

EnvironmentFile¶

The argument passed should be an absolute filename or wildcard expression, optionally prefixed with "-", 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 (more specifically, 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 the order they are specified and the later setting will override the earlier setting. Optional. Type list of uniline.

PassEnvironment¶

Variables passed from this setting are overridden by those passed from "Environment" or "EnvironmentFile".

Example:

    PassEnvironment=VAR1 VAR2 VAR3

passes three variables "VAR1", "VAR2", "VAR3" with the values set for those variables in PID1.

See environ(7) for details about environment variables. Optional. Type list of uniline.

StandardInput¶

If "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, 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 executed process waits until the current controlling process releases the terminal.

"tty-force" is similar to "tty", but the executed process is forcefully and immediately made the controlling process of the terminal, potentially removing previous controlling processes from the terminal.

"tty-fail" is similar to "tty" but if the terminal already has a controlling process start-up of the executed process fails.

The "socket" option is only valid in socket-activated services, and only when the socket configuration file (see systemd.socket(5) for details) specifies a single socket 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 with daemons designed for use with the traditional inetd(8) daemon.

The "fd" option connects the input stream to a single file descriptor provided by a socket unit. A custom named file descriptor can be specified as part of this option, after a ":" (e.g. "fd:foobar"). If no name is specified, "stdin" is assumed (i.e. "fd" is equivalent to "fd:stdin"). At least one socket unit defining such name must be explicitly provided via the "Sockets" option, and file descriptor name may differ from the name of its containing socket unit. If multiple matches are found, the first one will be used. See "FileDescriptorName" in systemd.socket(5) for more details about named descriptors and ordering.

This setting defaults to "null". Optional. Type enum. choice: 'null', 'tty', 'tty-force', 'tty-fail', 'socket', 'fd'.

StandardOutput¶

"inherit" duplicates the file descriptor of standard input for standard output.

"null" connects standard output to /dev/null, i.e. everything written to it will be lost.

"tty" connects standard output to a tty (as configured via "TTYPath", see below). If the TTY is used for output 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 terminal.

"journal" connects standard output with the journal which is accessible via journalctl(1). Note that everything that is written to syslog or kmsg (see below) is implicitly stored in the journal as well, the specific two options listed below are hence supersets of this one.

"syslog" connects standard output to the syslog(3) system syslog service, in addition to the journal. Note that the journal daemon is usually configured to forward everything it receives to syslog anyway, in which case this option is no different from "journal".

"kmsg" connects standard output with the kernel log buffer which is accessible via dmesg(1), in addition to the journal. The journal daemon might be configured to send all logs to kmsg anyway, in which case this option is no different from "journal".

"journal+console", "syslog+console" and "kmsg+console" work in a similar way as the three options above but copy the output to the system console as well.

"socket" connects standard output to a socket acquired via socket activation. The semantics are similar to the same option of "StandardInput".

The "fd" option connects the output stream to a single file descriptor provided by a socket unit. A custom named file descriptor can be specified as part of this option, after a ":" (e.g. "fd:foobar"). If no name is specified, "stdout" is assumed (i.e. "fd" is equivalent to "fd:stdout"). At least one socket unit defining such name must be explicitly provided via the "Sockets" option, and file descriptor name may differ from the name of its containing socket unit. If multiple matches are found, the first one will be used. See "FileDescriptorName" in systemd.socket(5) for more details about named descriptors and ordering.

If the standard output (or error output, see below) of a unit is connected to the journal, syslog or the kernel log buffer, the unit will implicitly gain a dependency of type "After" on systemd-journald.socket (also see the automatic dependencies section above).

This setting defaults to the value set with "DefaultStandardOutput" in systemd-system.conf(5), which defaults to "journal". Note that setting this parameter might result in additional dependencies to be added to the unit (see above). Optional. Type enum. choice: 'inherit', 'null', 'tty', 'journal', 'syslog', 'kmsg', 'journal+console', 'syslog+console', 'kmsg+console', 'socket', 'fd'.

StandardError¶

This setting defaults to the value set with "DefaultStandardError" in systemd-system.conf(5), which defaults to "inherit". Note that setting this parameter might result in additional dependencies to be added to the unit (see above). Optional. Type uniline.

TTYPath¶

TTYReset¶

TTYVHangup¶

TTYVTDisallocate¶

SyslogIdentifier¶

SyslogFacility¶

SyslogLevel¶

SyslogLevelPrefix¶

TimerSlackNSec¶

LimitCPU¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitFSIZE¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitDATA¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitSTACK¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitCORE¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitRSS¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitNOFILE¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitAS¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitNPROC¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitMEMLOCK¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitLOCKS¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitSIGPENDING¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitMSGQUEUE¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitNICE¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitRTPRIO¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

LimitRTTIME¶

Note that most process resource limits configured with these options are per-process, and processes may fork in order to acquire a new set of resources that are accounted independently of the original process, and may thus escape limits set. Also note that "LimitRSS" is not implemented on Linux, and setting it has no effect. Often it is advisable to prefer the resource controls listed in systemd.resource-control(5) over these per-process limits, as they apply to services as a whole, may be altered dynamically at runtime, and are generally more expressive. For example, "MemoryLimit" is a more powerful (and working) replacement for "LimitRSS".

For system units these resource limits may be chosen freely. For user units however (i.e. units run by a per-user instance of systemd(1)), these limits are bound by (possibly more restrictive) per-user limits enforced by the OS.

Resource limits not configured explicitly for a unit default to the value configured in the various "DefaultLimitCPU", "DefaultLimitFSIZE", X options available in systemd-system.conf(5), and X if not configured there X the kernel or per-user defaults, as defined by the OS (the latter only for user services, see above). Optional. Type uniline.

PAMName¶

CapabilityBoundingSet¶

AmbientCapabilities¶

 Ambient capability sets are useful if you want to execute a process as a
non-privileged user but still want to give it some capabilities.  Note that in this case option
C<keep-caps> is automatically added to C<SecureBits> to retain the
capabilities over the user change. C<AmbientCapabilities> does not affect commands prefixed
with C<+>. I<< Optional. Type uniline.  >>

SecureBits¶

ReadWritePaths¶

Paths listed in "ReadWritePaths" are accessible from within the namespace with the same access modes as from outside of it. Paths listed in "ReadOnlyPaths" are accessible for reading only, writing will be refused even if the usual file access controls would permit this. Nest "ReadWritePaths" inside of "ReadOnlyPaths" in order to provide writable subdirectories within read-only directories. Use "ReadWritePaths" in order to whitelist specific paths for write access if "ProtectSystem=strict" is used. Paths listed in "InaccessiblePaths" will be made inaccessible for processes inside the namespace (along with everything below them in the file system hierarchy).

Note that restricting access with these options does not extend to submounts of a directory that are created later on. Non-directory paths may be specified as well. These options may be specified more than once, in which case all paths 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 effect.

Paths in "ReadWritePaths", "ReadOnlyPaths" and "InaccessiblePaths" may be prefixed with "-", in which case they will be ignored when they do not 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. Note that the effect of these settings may be undone by privileged processes. In order to set up an effective sandboxed environment for a unit it is thus recommended to combine these settings with either "CapabilityBoundingSet=~CAP_SYS_ADMIN" or "SystemCallFilter=~@mount". Optional. Type list of uniline.

ReadOnlyPaths¶

Paths listed in "ReadWritePaths" are accessible from within the namespace with the same access modes as from outside of it. Paths listed in "ReadOnlyPaths" are accessible for reading only, writing will be refused even if the usual file access controls would permit this. Nest "ReadWritePaths" inside of "ReadOnlyPaths" in order to provide writable subdirectories within read-only directories. Use "ReadWritePaths" in order to whitelist specific paths for write access if "ProtectSystem=strict" is used. Paths listed in "InaccessiblePaths" will be made inaccessible for processes inside the namespace (along with everything below them in the file system hierarchy).

Note that restricting access with these options does not extend to submounts of a directory that are created later on. Non-directory paths may be specified as well. These options may be specified more than once, in which case all paths 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 effect.

Paths in "ReadWritePaths", "ReadOnlyPaths" and "InaccessiblePaths" may be prefixed with "-", in which case they will be ignored when they do not 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. Note that the effect of these settings may be undone by privileged processes. In order to set up an effective sandboxed environment for a unit it is thus recommended to combine these settings with either "CapabilityBoundingSet=~CAP_SYS_ADMIN" or "SystemCallFilter=~@mount". Optional. Type list of uniline.

InaccessiblePaths¶

Paths listed in "ReadWritePaths" are accessible from within the namespace with the same access modes as from outside of it. Paths listed in "ReadOnlyPaths" are accessible for reading only, writing will be refused even if the usual file access controls would permit this. Nest "ReadWritePaths" inside of "ReadOnlyPaths" in order to provide writable subdirectories within read-only directories. Use "ReadWritePaths" in order to whitelist specific paths for write access if "ProtectSystem=strict" is used. Paths listed in "InaccessiblePaths" will be made inaccessible for processes inside the namespace (along with everything below them in the file system hierarchy).

Note that restricting access with these options does not extend to submounts of a directory that are created later on. Non-directory paths may be specified as well. These options may be specified more than once, in which case all paths 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 effect.

Paths in "ReadWritePaths", "ReadOnlyPaths" and "InaccessiblePaths" may be prefixed with "-", in which case they will be ignored when they do not 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. Note that the effect of these settings may be undone by privileged processes. In order to set up an effective sandboxed environment for a unit it is thus recommended to combine these settings with either "CapabilityBoundingSet=~CAP_SYS_ADMIN" or "SystemCallFilter=~@mount". Optional. Type list of uniline.

PrivateTmp¶

PrivateDevices¶

PrivateNetwork¶

PrivateUsers¶

This setting is particularly useful in conjunction with "RootDirectory", as the need to synchronize the user and group databases in the root directory and on the host is reduced, as the only users and groups who need to be matched are "root", "nobody" and the unit's own user and group. Optional. Type boolean.

ProtectSystem¶

ProtectHome¶

ProtectKernelTunables¶

ProtectControlGroups¶

MountFlags¶

UtmpIdentifier¶

UtmpMode¶

SELinuxContext¶

AppArmorProfile¶

SmackProcessLabel¶

The value may be prefixed by "-", in which case all errors will be ignored. An empty value may be specified to unset previous assignments. This does not affect commands prefixed with "+". Optional. Type uniline.

IgnoreSIGPIPE¶

NoNewPrivileges¶

SystemCallFilter¶

Note that strict system call filters may impact execution and error handling code paths of the service invocation. Specifically, access to the execve system call is required for the execution of the service binary X if it is blocked service invocation will necessarily fail. Also, if execution of the service binary fails for some reason (for example: missing service executable), the error handling logic might require access to an additional set of system calls in order to process and log this failure correctly. It might be necessary to temporarily disable system call filters in order to simplify debugging of such failures.

If you specify both types of this option (i.e. whitelisting and blacklisting), the first encountered will take precedence and will dictate the default action (termination or approval of a system call). Then the next occurrences of this option will add or delete the listed system calls from the set of the filtered system calls, depending of its type and the default action. (For example, if you have started with a whitelisting of read and write, and right after it add a blacklisting of write, then write will be removed from the set.)

As the number of possible system calls is large, predefined sets of system calls are provided. A set starts with "@" character, followed by name of the set. Currently predefined system call setsSetDescription@basic-ioSystem calls for basic I/O: reading, writing, seeking, file descriptor duplication and closing (read(2), write(2), and related calls)@clockSystem calls for changing the system clock (adjtimex(2), settimeofday(2), and related calls)@cpu-emulationSystem calls for CPU emulation functionality (vm86(2) and related calls)@debugDebugging, performance monitoring and tracing functionality (ptrace(2), perf_event_open(2) and related calls)@io-eventEvent loop system calls (poll(2), select(2), epoll(7), eventfd(2) and related calls)@ipcPipes, SysV IPC, POSIX Message Queues and other IPC (mq_overview(7), svipc(7))@keyringKernel keyring access (keyctl(2) and related calls)@moduleKernel module control (init_module(2), delete_module(2) and related calls)@mountFile system mounting and unmounting (mount(2), chroot(2), and related calls)@network-ioSocket I/O (including local AF_UNIX): socket(7), unix(7)@obsoleteUnusual, obsolete or unimplemented (create_module(2), gtty(2), X)@privilegedAll system calls which need super-user capabilities (capabilities(7))@processProcess control, execution, namespaces (clone(2), kill(2), namespaces(7), X@raw-ioRaw I/O port access (ioperm(2), iopl(2), pciconfig_read(), X)@resourcesSystem calls for changing resource limits, memory and scheduling parameters (setrlimit(2), setpriority(2), X) Note that as new system calls are added to the kernel, additional system calls might be added to the groups above, so the contents of the sets may change between systemd versions.

It is recommended to combine the file system namespacing related options with "SystemCallFilter=~@mount", in order to prohibit the unit's processes to undo the mappings. Specifically these are the options "PrivateTmp", "PrivateDevices", "ProtectSystem", "ProtectHome", "ProtectKernelTunables", "ProtectControlGroups", "ReadOnlyPaths", "InaccessiblePaths" and "ReadWritePaths". Optional. Type list of uniline.

SystemCallErrorNumber¶

SystemCallArchitectures¶

RestrictAddressFamilies¶

Use this option to limit exposure of processes to remote systems, in particular via exotic network protocols. Note that in most cases, the local "AF_UNIX" address family should be included in the configured whitelist as it is frequently used for local communication, including for syslog(2) logging. This does not affect commands prefixed with "+". Optional. Type uniline.

ProtectKernelModules¶

Personality¶

RuntimeDirectory¶

RuntimeDirectoryMode¶

MemoryDenyWriteExecute¶

RestrictRealtime¶

KillMode¶

If set to "control-group", all remaining processes in the control group of this unit will be killed on unit stop (for services: after the stop command is executed, as configured with "ExecStop"). If set to "process", only the main process itself is killed. If set to "mixed", the "SIGTERM" signal (see below) is sent to the main process while the subsequent "SIGKILL" signal (see below) is sent to all remaining processes of the unit's control group. If set to "none", no process is killed. In this case, only the stop command will be executed on unit stop, but no process be killed otherwise. Processes remaining alive after stop are left in their control group and the control group continues to exist after stop unless it is empty.

Processes will first be terminated via "SIGTERM" (unless the signal to send is changed via "KillSignal"). Optionally, this is immediately followed by a "SIGHUP" (if enabled with "SendSIGHUP"). If then, after a delay (configured via the "TimeoutStopSec" option), processes still remain, the termination request is repeated with the "SIGKILL" signal (unless this is disabled via the "SendSIGKILL" option). See kill(2) for more information.

Defaults to "control-group". Optional. Type uniline.

KillSignal¶

Note that, right after sending the signal specified in this setting, systemd will always send "SIGCONT", to ensure that even suspended tasks can be terminated cleanly. Optional. Type uniline.

SendSIGHUP¶

SendSIGKILL¶

Type¶

If set to "simple" (the default if neither "Type" nor "BusName", but "ExecStart" are specified), it is expected that the process configured with "ExecStart" is the main process of the service. In this mode, if the process offers functionality to other processes on the system, its communication channels should be installed before the daemon is started up (e.g. sockets set up by systemd, via socket activation), as systemd will immediately proceed starting follow-up units.

If set to "forking", it is expected that the process configured with "ExecStart" will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main daemon process. This is the behavior of traditional UNIX daemons. If this setting is used, it is recommended to also use the "PIDFile" option, so that systemd can identify the main process of the daemon. systemd will proceed with starting follow-up units as soon as the parent process exits.

Behavior of "oneshot" is similar to "simple"; however, it is expected that the process has to exit before systemd starts follow-up units. "RemainAfterExit" is particularly useful for this type of service. This is the implied default if neither "Type" or "ExecStart" are specified.

Behavior of "dbus" is similar to "simple"; however, it is expected that the daemon acquires a name on the D-Bus bus, as configured by "BusName". systemd will proceed with starting follow-up units after the D-Bus bus name has been acquired. Service units with this option configured implicitly gain dependencies on the dbus.socket unit. This type is the default if "BusName" is specified.

Behavior of "notify" is similar to "simple"; however, it is expected that the daemon sends a notification message via sd_notify(3) or an equivalent call when it has finished starting up. systemd will proceed with starting follow-up units after this notification message has been sent. If this option is used, "NotifyAccess" (see below) should be set to open access to the notification socket provided by systemd. If "NotifyAccess" is missing or set to "none", it will be forcibly set to "main". Note that currently "Type""notify" will not work if used in combination with "PrivateNetwork""yes".

Behavior of "idle" is very similar to "simple"; however, actual execution of the service binary is delayed until all active jobs are dispatched. This may be used to avoid interleaving of output of shell services with the status output on the console. Note that this type is useful only to improve console output, it is not useful as a general unit ordering tool, and the effect of this service type is subject to a 5s time-out, after which the service binary is invoked anyway. Optional. Type uniline.

RemainAfterExit¶

GuessMainPID¶

PIDFile¶

BusName¶

ExecStart¶

Unless "Type" is "oneshot", exactly one command must be given. When "Type=oneshot" is used, zero or more commands may be specified. Commands may be specified by providing multiple command lines in the same directive, or alternatively, this directive may be specified more than once with the same effect. If the empty string is assigned to this option, the list of commands to start is reset, prior assignments of this option will have no effect. If no "ExecStart" is specified, then the service must have "RemainAfterExit=yes" set.

For each of the specified commands, the first argument must be an absolute path to an executable. Optionally, if this file name is prefixed with "@", the second token will be passed as "argv[0]" to the executed process, followed by the further arguments specified. If the absolute filename is prefixed with "-", an exit code of the command normally considered a failure (i.e. non-zero exit status or abnormal exit due to signal) is ignored and considered success. If the absolute path is prefixed with "+" then it is executed with full privileges. "@", "-", and "+" may be used together and they can appear in any order.

If more than one command is specified, the commands are invoked sequentially in the order they appear in the unit file. If one of the commands fails (and is not prefixed with "-"), other lines are not executed, and the unit is considered failed.

Unless "Type=forking" is set, the process started via this command line will be considered the main process of the daemon. Optional. Type list of uniline.

ExecStartPre¶

If any of those commands (not prefixed with "-") fail, the rest are not executed and the unit is considered failed.

"ExecStart" commands are only run after all "ExecStartPre" commands that were not prefixed with a "-" exit successfully.

"ExecStartPost" commands are only run after the service has started successfully, as determined by "Type" (i.e. the process has been started for "Type=simple" or "Type=idle", the process exits successfully for "Type=oneshot", the initial process exits successfully for "Type=forking", "READY=1" is sent for "Type=notify", or the "BusName" has been taken for "Type=dbus").

Note that "ExecStartPre" may not be used to start long-running processes. All processes forked off by processes invoked via "ExecStartPre" will be killed before the next service process is run.

Note that if any of the commands specified in "ExecStartPre", "ExecStart", or "ExecStartPost" fail (and are not prefixed with "-", see above) or time out before the service is fully up, execution continues with commands specified in "ExecStopPost", the commands in "ExecStop" are skipped. Optional. Type list of uniline.

ExecStartPost¶

If any of those commands (not prefixed with "-") fail, the rest are not executed and the unit is considered failed.

"ExecStart" commands are only run after all "ExecStartPre" commands that were not prefixed with a "-" exit successfully.

"ExecStartPost" commands are only run after the service has started successfully, as determined by "Type" (i.e. the process has been started for "Type=simple" or "Type=idle", the process exits successfully for "Type=oneshot", the initial process exits successfully for "Type=forking", "READY=1" is sent for "Type=notify", or the "BusName" has been taken for "Type=dbus").

Note that "ExecStartPre" may not be used to start long-running processes. All processes forked off by processes invoked via "ExecStartPre" will be killed before the next service process is run.

Note that if any of the commands specified in "ExecStartPre", "ExecStart", or "ExecStartPost" fail (and are not prefixed with "-", see above) or time out before the service is fully up, execution continues with commands specified in "ExecStopPost", the commands in "ExecStop" are skipped. Optional. Type list of uniline.

ExecReload¶

One additional, special environment variable is set: if known, $MAINPID is set to the main process of the daemon, and may be used for command lines like the following:

Note however that reloading a daemon by sending a signal (as with the example line above) is usually not a good choice, because this is an asynchronous operation and hence not suitable to order reloads of multiple services against each other. It is strongly recommended to set "ExecReload" to a command that not only triggers a configuration reload of the daemon, but also synchronously waits for it to complete. Optional. Type list of uniline.

ExecStop¶

Note that it is usually not sufficient to specify a command for this setting that only asks the service to terminate (for example, by queuing some form of termination signal for it), but does not wait for it to do so. Since the remaining processes of the services are killed using "SIGKILL" immediately after the command exited, this would not result in a clean stop. The specified command should hence be a synchronous operation, not an asynchronous one.

Note that the commands specified in "ExecStop" are only executed when the service started successfully first. They are not invoked if the service was never started at all, or in case its start-up failed, for example because any of the commands specified in "ExecStart", "ExecStartPre" or "ExecStartPost" failed (and weren't prefixed with "-", see above) or timed out. Use "ExecStopPost" to invoke commands when a service failed to start up correctly and is shut down again.

It is recommended to use this setting for commands that communicate with the service requesting clean termination. When the commands specified with this option are executed it should be assumed that the service is still fully up and is able to react correctly to all commands. For post-mortem clean-up steps use "ExecStopPost" instead. Optional. Type list of uniline.

ExecStopPost¶

It is recommended to use this setting for clean-up operations that shall be executed even when the service failed to start up correctly. Commands configured with this setting need to be able to operate even if the service failed starting up half-way and left incompletely initialized data around. As the service's processes have been terminated already when the commands specified with this setting are executed they should not attempt to communicate with them.

Note that all commands that are configured with this setting are invoked with the result code of the service, as well as the main process' exit code and status, set in the $SERVICE_RESULT, $EXIT_CODE and $EXIT_STATUS environment variables, see systemd.exec(5) for details. Optional. Type list of uniline.

RestartSec¶

TimeoutStartSec¶

TimeoutStopSec¶

TimeoutSec¶

RuntimeMaxSec¶

WatchdogSec¶

Restart¶

Takes one of "no", "on-success", "on-failure", "on-abnormal", "on-watchdog", "on-abort", or "always". If set to "no" (the default), the service will not be restarted. If set to "on-success", it will be restarted only when the service process exits cleanly. In this context, a clean exit means an exit code of 0, or one of the signals "SIGHUP", "SIGINT", "SIGTERM" or "SIGPIPE", and additionally, exit statuses and signals specified in "SuccessExitStatus". If set to "on-failure", the service will be restarted when the process exits with a non-zero exit code, is terminated by a signal (including on core dump, but excluding the aforementioned four signals), when an operation (such as service reload) times out, and when the configured watchdog timeout is triggered. If set to "on-abnormal", the service will be restarted when the process is terminated by a signal (including on core dump, excluding the aforementioned four signals), when an operation times out, or when the watchdog timeout is triggered. If set to "on-abort", the service will be restarted only if the service process exits due to an uncaught signal not specified as a clean exit status. If set to "on-watchdog", the service will be restarted only if the watchdog timeout for the service expires. If set to "always", the service will be restarted regardless of whether it exited cleanly or not, got terminated abnormally by a signal, or hit a timeout.

As exceptions to the setting above, the service will not be restarted if the exit code or signal is specified in "RestartPreventExitStatus" (see below). Also, the services will always be restarted if the exit code or signal is specified in "RestartForceExitStatus" (see below).

Setting this to "on-failure" is the recommended choice for long-running services, in order to increase reliability by attempting automatic recovery from errors. For services that shall be able to terminate on their own choice (and avoid immediate restarting), "on-abnormal" is an alternative choice. Optional. Type enum. choice: 'no', 'on-success', 'on-failure', 'on-abnormal', 'on-watchdog', 'on-abort', 'always'.

SuccessExitStatus¶

    SuccessExitStatus=1 2 8 SIGKILL

ensures that exit codes 1, 2, 8 and the termination signal "SIGKILL" are considered clean service terminations.

Note that if a process has a signal handler installed and exits by calling _exit(2) in response to a signal, the information about the signal is lost. Programs should instead perform cleanup and kill themselves with the same signal instead. See Proper handling of SIGINT/SIGQUIT X How to be a proper program.

This option may appear more than once, in which case the list of successful exit statuses is merged. If the empty string is assigned to this option, the list is reset, all prior assignments of this option will have no effect. Optional. Type uniline.

RestartPreventExitStatus¶

    RestartPreventExitStatus=1 6 SIGABRT

ensures that exit codes 1 and 6 and the termination signal "SIGABRT" will not result in automatic service restarting. This option may appear more than once, in which case the list of restart-preventing statuses is merged. If the empty string is assigned to this option, the list is reset and all prior assignments of this option will have no effect. Optional. Type uniline.

RestartForceExitStatus¶

PermissionsStartOnly¶

RootDirectoryStartOnly¶

NonBlocking¶

NotifyAccess¶

Sockets¶

Note that the same socket file descriptors may be passed to multiple processes simultaneously. Also note that a different service may be activated on incoming socket traffic than the one which is ultimately configured to inherit the socket file descriptors. Or, in other words: the "Service" setting of .socket units does not have to match the inverse of the "Sockets" setting of the .service it refers to.

This option may appear more than once, in which case the list of socket units is merged. If the empty string is assigned to this option, the list of sockets is reset, and all prior uses of this setting will have no effect. Optional. Type uniline.

FailureAction¶

FileDescriptorStoreMax¶

USBFunctionDescriptors¶

USBFunctionStrings¶