# PODNAME: Config::Model::models::Systemd::Section::Service
# ABSTRACT:  Configuration class Systemd::Section::Service
=head1 NAME

Config::Model::models::Systemd::Section::Service - Configuration class Systemd::Section::Service

=head1 DESCRIPTION

Configuration classes used by L<Config::Model>

A unit configuration file whose name ends in
.service encodes information about a process
controlled and supervised by systemd.
This man page lists the configuration options specific to
this unit type. See
L<systemd.unit(5)|"https://manpages.debian.org/cgi-bin/man.cgi?query=systemd.unit&sektion=5&manpath=Debian+unstable+sid">
for the common options of all unit configuration files. The common
configuration items are configured in the generic
C<[Unit]> and C<[Install]>
sections. The service specific configuration options are
configured in the C<[Service]> section.
Additional options are listed in
L<systemd.exec(5)|"https://manpages.debian.org/cgi-bin/man.cgi?query=systemd.exec&sektion=5&manpath=Debian+unstable+sid">,
which define the execution environment the commands are executed
in, and in
L<systemd.kill(5)|"https://manpages.debian.org/cgi-bin/man.cgi?query=systemd.kill&sektion=5&manpath=Debian+unstable+sid">,
which define the way the processes of the service are terminated,
and in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?query=systemd.resource-control&sektion=5&manpath=Debian+unstable+sid">,
which configure resource control settings for the processes of the
service.
If a service is requested under a certain name but no unit
configuration file is found, systemd looks for a SysV init script
by the same name (with the .service suffix
removed) and dynamically creates a service unit from that script.
This is useful for compatibility with SysV. Note that this
compatibility is quite comprehensive but not 100%. For details
about the incompatibilities, see the Incompatibilities
with SysV document.
This configuration class was generated from systemd documentation.
by L<parse-man.pl|https://github.com/dod38fr/config-model-systemd/contrib/parse-man.pl>


=head1 Elements

=head2 CPUAccounting

Turn on CPU usage accounting for this unit. Takes a
boolean argument. Note that turning on CPU accounting for
one unit will also implicitly turn it on for all units
contained in the same slice and for all its parent slices
and the units contained therein. The system default for this
setting may be controlled with
C<DefaultCPUAccounting> in
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">. I<< Optional. Type boolean.  >> 

=head2 CPUShares

Assign the specified CPU time share weight to the
processes executed. These options take an integer value and
control the C<cpu.shares> control group
attribute. The allowed range is 2 to 262144. Defaults to
1024. For details about this control group attribute, see
sched-design-CFS.txt.
The available CPU time is split up among all units within
one slice relative to their CPU time share weight.While C<StartupCPUShares> only
applies to the startup phase of the system,
C<CPUShares> applies to normal runtime of
the system, and if the former is not set also to the startup
phase. Using C<StartupCPUShares> allows
prioritizing specific services at boot-up differently than
during normal runtime.These options imply
C<C<CPUAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 StartupCPUShares

Assign the specified CPU time share weight to the
processes executed. These options take an integer value and
control the C<cpu.shares> control group
attribute. The allowed range is 2 to 262144. Defaults to
1024. For details about this control group attribute, see
sched-design-CFS.txt.
The available CPU time is split up among all units within
one slice relative to their CPU time share weight.While C<StartupCPUShares> only
applies to the startup phase of the system,
C<CPUShares> applies to normal runtime of
the system, and if the former is not set also to the startup
phase. Using C<StartupCPUShares> allows
prioritizing specific services at boot-up differently than
during normal runtime.These options imply
C<C<CPUAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 CPUQuota

Assign the specified CPU time quota to the processes
executed. Takes a percentage value, suffixed with "%". The
percentage specifies how much CPU time the unit shall get at
maximum, relative to the total CPU time available on one
CPU. Use values > 100% for allotting CPU time on more than
one CPU. This controls the
C<cpu.cfs_quota_us> control group
attribute. For details about this control group attribute,
see sched-design-CFS.txt.Example: C<CPUQuota>20% ensures that
the executed processes will never get more than 20% CPU time
on one CPU.Implies C<C<CPUAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 MemoryAccounting

Turn on process and kernel memory accounting for this
unit. Takes a boolean argument. Note that turning on memory
accounting for one unit will also implicitly turn it on for
all units contained in the same slice and for all its parent
slices and the units contained therein. The system default
for this setting may be controlled with
C<DefaultMemoryAccounting> in
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">. I<< Optional. Type boolean.  >> 

=head2 MemoryLimit

Specify the limit on maximum memory usage of the
executed processes. The limit specifies how much process and
kernel memory can be used by tasks in this unit. 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. If assigned the special value
C<infinity>, no memory limit is applied. This
controls the C<memory.limit_in_bytes>
control group attribute. For details about this control
group attribute, see memory.txt.Implies C<C<MemoryAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 TasksAccounting

Turn on task accounting for this unit. Takes a
boolean argument. If enabled, the system manager will keep
track of the number of tasks in the unit. The number of
tasks accounted this way includes both kernel threads and
userspace processes, with each thread counting
individually. Note that turning on tasks accounting for one
unit will also implicitly turn it on for all units contained
in the same slice and for all its parent slices and the
units contained therein. The system default for this setting
may be controlled with
C<DefaultTasksAccounting> in
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">. I<< Optional. Type boolean.  >> 

=head2 TasksMax

Specify the maximum number of tasks that may be
created in the unit. This ensures that the number of tasks
accounted for the unit (see above) stays below a specific
limit. If assigned the special value
C<infinity>, no tasks limit is applied. This
controls the C<pids.max> control group
attribute. For details about this control group attribute,
see pids.txt.Implies C<C<TasksAccounting>true>. The
system default for this setting may be controlled with
C<DefaultTasksMax> in
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">. I<< Optional. Type uniline.  >> 

=head2 BlockIOAccounting

Turn on Block I/O accounting for this unit. Takes a
boolean argument. Note that turning on block I/O accounting
for one unit will also implicitly turn it on for all units
contained in the same slice and all for its parent slices
and the units contained therein. The system default for this
setting may be controlled with
C<DefaultBlockIOAccounting> in
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">. I<< Optional. Type boolean.  >> 

=head2 BlockIOWeight

Set the default overall block I/O weight for
the executed processes. Takes a single weight value (between
10 and 1000) to set the default block I/O weight. This controls
the C<blkio.weight> control group attribute,
which defaults to 500. For details about this control group
attribute, see blkio-controller.txt.
The available I/O bandwidth is split up among all units within
one slice relative to their block I/O weight.While C<StartupBlockIOWeight> only
applies to the startup phase of the system,
C<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
C<C<BlockIOAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 StartupBlockIOWeight

Set the default overall block I/O weight for
the executed processes. Takes a single weight value (between
10 and 1000) to set the default block I/O weight. This controls
the C<blkio.weight> control group attribute,
which defaults to 500. For details about this control group
attribute, see blkio-controller.txt.
The available I/O bandwidth is split up among all units within
one slice relative to their block I/O weight.While C<StartupBlockIOWeight> only
applies to the startup phase of the system,
C<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
C<C<BlockIOAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 BlockIODeviceWeight

Set the per-device overall block I/O weight for the
executed processes. Takes a space-separated pair of a file
path and a weight value to specify the device specific
weight value, between 10 and 1000. (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
C<blkio.weight_device> control group
attribute, which defaults to 1000. Use this option multiple
times to set weights for multiple devices. For details about
this control group attribute, see blkio-controller.txt.Implies
C<C<BlockIOAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 BlockIOReadBandwidth

Set the per-device overall block I/O 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
a 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 used. If the bandwidth is suffixed with K, M, G, or T,
the specified bandwidth is parsed as Kilobytes, Megabytes,
Gigabytes, or Terabytes, respectively, to the base of
1000. (Example:
"/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0 5M"). This
controls the C<blkio.read_bps_device> and
C<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.
Implies
C<C<BlockIOAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 BlockIOWriteBandwidth

Set the per-device overall block I/O 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
a 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 used. If the bandwidth is suffixed with K, M, G, or T,
the specified bandwidth is parsed as Kilobytes, Megabytes,
Gigabytes, or Terabytes, respectively, to the base of
1000. (Example:
"/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0 5M"). This
controls the C<blkio.read_bps_device> and
C<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.
Implies
C<C<BlockIOAccounting>true>. I<< Optional. Type uniline.  >> 

=head2 DeviceAllow

Control access to specific device nodes by the
executed processes. Takes two space-separated strings: a
device node specifier followed by a combination of
r, w,
m to control
reading, writing,
or creation of the specific device node(s) by the unit
(mknod), respectively. This controls
the C<devices.allow> and
C<devices.deny> control group
attributes. For details about these control group
attributes, see devices.txt.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
C<char-> or C<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
C<*> and C<?>
wildcards. Examples: /dev/sda5 is a
path to a device node, referring to an ATA or SCSI block
device. C<char-pts> and
C<char-alsa> are specifiers for all pseudo
TTYs and all ALSA sound devices,
respectively. C<char-cpu/*> is a specifier
matching all CPU related device groups. I<< Optional. Type uniline.  >> 

=head2 DevicePolicy

Control the policy for allowing device access:
strictmeans to only allow types of access that are
explicitly specified.closedin addition, allows access to standard pseudo
devices including
/dev/null,
/dev/zero,
/dev/full,
/dev/random, and
/dev/urandom.
auto
in addition, allows access to all devices if no
explicit C<DeviceAllow> is present.
This is the default.
I<< Optional. Type enum. choice: 'auto', 'closed', 'strict'.  >> 

=head2 NetClass

Configures a network class number to assign to the
unit. This value will be set to the
C<net_cls.class_id> property of the
C<net_cls> cgroup of the unit. The directive
accepts a numerical value (for fixed number assignment) and the keyword
C<auto> (for dynamic allocation). Network traffic of
all processes inside the unit will have the network class ID assigned
by the kernel. Also see
the kernel docs for
net_cls controller
and
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">.
I<< Optional. Type uniline.  >> 

=head2 Slice

The name of the slice unit to place the unit
in. Defaults to system.slice for all
non-instantiated units of all unit types (except for slice
units themselves see below). Instance units are by default
placed in a subslice of system.slice
that is named after the template name.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. I<< Optional. Type uniline.  >> 

=head2 Delegate

Turns on delegation of further resource control
partitioning to processes of the unit. For unprivileged
services (i.e. those using the C<User>
setting), this allows processes to create a subhierarchy
beneath its control group path. For privileged services and
scopes, this ensures the processes will have all control
group controllers enabled. I<< Optional. Type uniline.  >> 

=head2 WorkingDirectory

Takes an absolute directory path, or the
special value C<~>. Sets the working directory
for executed processes. If set to C<~>, the
home directory of the user specified in
C<User> is used. If 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 user. If
the setting is prefixed with the C<->
character, a missing working directory is not considered
fatal. Note that setting this parameter might result in
additional dependencies to be added to the unit (see
above). I<< Optional. Type uniline.  >> 

=head2 RootDirectory

Takes an absolute directory path. Sets the
root directory for executed processes, with the L<chroot(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>chroot&C<sektion>2&C<manpath>Debian+unstable+sid">
system call. If this is used, it must be ensured that the
process binary and all its auxiliary files are available in
the chroot() jail. Note that setting this
parameter might result in additional dependencies to be added
to the unit (see above). I<< Optional. Type uniline.  >> 

=head2 User

Sets the Unix user or group that the processes
are executed as, respectively. Takes a single user or group
name or ID as argument. If no group is set, the default group
of the user is chosen. I<< Optional. Type uniline.  >> 

=head2 Group

Sets the Unix user or group that the processes
are executed as, respectively. Takes a single user or group
name or ID as argument. If no group is set, the default group
of the user is chosen. I<< Optional. Type uniline.  >> 

=head2 SupplementaryGroups

Sets the supplementary Unix groups the
processes are executed 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 supplementary
groups. When the empty string is assigned, the list of
supplementary groups is reset, and all assignments prior to
this one will have no effect. In any way, this option does not
override, but extends the list of supplementary groups
configured in the system group database for the
user. I<< Optional. Type list of uniline.  >> 

=head2 Nice

Sets the default nice level (scheduling
priority) for executed processes. Takes an integer between -20
(highest priority) and 19 (lowest priority). See
L<setpriority(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setpriority&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type integer.  >> 

=head2 OOMScoreAdjust

Sets the adjustment level for the
Out-Of-Memory killer for executed processes. Takes an integer
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
for details. I<< Optional. Type integer.  >> 

=head2 IOSchedulingClass

Sets the I/O scheduling class for executed
processes. Takes an integer between 0 and 3 or one of the
strings none, realtime,
best-effort or idle. See
L<ioprio_set(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>ioprio_set&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type integer.  >> 

=head2 IOSchedulingPriority

Sets the I/O scheduling priority for executed
processes. Takes an integer between 0 (highest priority) and 7
(lowest priority). The available priorities depend on the
selected I/O scheduling class (see above). See
L<ioprio_set(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>ioprio_set&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type integer.  >> 

=head2 CPUSchedulingPolicy

Sets the CPU scheduling policy for executed
processes. Takes one of
other,
batch,
idle,
fifo or
rr. See
L<sched_setscheduler(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sched_setscheduler&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type enum. choice: 'other', 'batch', 'idle', 'fifo', 'rr'.  >> 

=head2 CPUSchedulingPriority

Sets the CPU scheduling priority for executed
processes. The available priority range depends on the
selected CPU scheduling policy (see above). For real-time
scheduling policies an integer between 1 (lowest priority) and
99 (highest priority) can be used. See
L<sched_setscheduler(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sched_setscheduler&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type uniline.  >> 

=head2 CPUSchedulingResetOnFork

Takes a boolean argument. If true, elevated
CPU scheduling priorities and policies will be reset when the
executed processes fork, and can hence not leak into child
processes. See
L<sched_setscheduler(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sched_setscheduler&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Defaults to false. I<< Optional. Type boolean.  >> 

=head2 CPUAffinity

Controls the CPU affinity of the executed
processes. Takes a list of CPU indices or ranges separated by
either whitespace or commas. CPU ranges are specified by the
lower and upper CPU indices separated by a dash.
This option may be specified more than once, in which case the
specified CPU affinity masks are merged. If the empty string
is assigned, the mask is reset, all assignments prior to this
will have no effect. See
L<sched_setaffinity(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sched_setaffinity&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type list of uniline.  >> 

=head2 UMask

Controls the file mode creation mask. Takes an
access mode in octal notation. See
L<umask(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>umask&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Defaults to 0022. I<< Optional. Type uniline.  >> 

=head2 Environment

Sets environment variables for executed
processes. Takes a space-separated list of variable
assignments. This 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 override the
earlier setting. If the empty string is assigned to this
option, the list of environment variables is reset, all prior
assignments have no effect. Variable expansion is not
performed 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:
C<Environment>"C<VAR1>word1 word2" C<VAR2>word3 "C<VAR3>$word 5 6"
gives three variables C<VAR1>,
C<VAR2>, C<VAR3>
with the values C<word1 word2>,
C<word3>, C<$word 5 6>.
See
L<environ(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>environ&C<sektion>7&C<manpath>Debian+unstable+sid">
for details about environment variables. I<< Optional. Type list of uniline.  >> 

=head2 EnvironmentFile

Similar to C<Environment> but
reads the environment variables from a text file. The text
file should contain new-line-separated variable assignments.
Empty lines, lines without an C<=> separator,
or lines starting with ; or # will be ignored,
which may be used for commenting. A line ending with a
backslash will be concatenated with the following one,
allowing multiline variable definitions. The parser strips
leading and trailing whitespace from the values of
assignments, unless you use double quotes (").The argument passed should be an absolute filename or
wildcard expression, optionally prefixed with
C<->, 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
C<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. I<< Optional. Type list of uniline.  >> 

=head2 PassEnvironment

Pass environment variables from the systemd system
manager to executed processes. Takes a space-separated list of variable
names. This option may be specified more than once, in which case all
listed variables will be set. If the empty string is assigned to this
option, the list of environment variables is reset, all prior
assignments have no effect. Variables that are not set in the system
manager will not be passed and will be silently ignored.Variables passed from this setting are overridden by those passed
from C<Environment> or
C<EnvironmentFile>.Example:
C<PassEnvironment>VAR1 VAR2 VAR3
passes three variables C<VAR1>,
C<VAR2>, C<VAR3>
with the values set for those variables in PID1.
See
L<environ(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>environ&C<sektion>7&C<manpath>Debian+unstable+sid">
for details about environment variables. I<< Optional. Type list of uniline.  >> 

=head2 StandardInput

Controls where file descriptor 0 (STDIN) of
the executed processes is connected to. Takes one of
null,
tty,
tty-force,
tty-fail or
socket.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
C<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
L<systemd.socket(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.socket&C<sektion>5&C<manpath>Debian+unstable+sid">
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
L<inetd(8)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>inetd&C<sektion>8&C<manpath>Debian+unstable+sid">
daemon.This setting defaults to
null. I<< Optional. Type enum. choice: 'null', 'tty', 'tty-force', 'tty-fail', 'socket'.  >> 

=head2 StandardOutput

Controls where file descriptor 1 (STDOUT) of
the executed processes is connected to. Takes one of
inherit,
null,
tty,
journal,
syslog,
kmsg,
journal+console,
syslog+console,
kmsg+console or
socket.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 C<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
L<journalctl(1)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>journalctl&C<sektion>1&C<manpath>Debian+unstable+sid">.
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
L<syslog(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>syslog&C<sektion>3&C<manpath>Debian+unstable+sid">
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
L<dmesg(1)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>dmesg&C<sektion>1&C<manpath>Debian+unstable+sid">,
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
C<StandardInput>.This setting defaults to the value set with
C<DefaultStandardOutput> in
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">,
which defaults to journal. Note that setting
this parameter might result in additional dependencies to be
added to the unit (see above). I<< Optional. Type enum. choice: 'inherit', 'null', 'tty', 'journal', 'syslog', 'kmsg', 'journal+console', 'syslog+console', 'kmsg+console', 'socket'.  >> 

=head2 StandardError

Controls where file descriptor 2 (STDERR) of
the executed processes is connected to. The available options
are identical to those of C<StandardOutput>,
with one exception: if set to inherit the
file descriptor used for standard output is duplicated for
standard error. This setting defaults to the value set with
C<DefaultStandardError> in
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">,
which defaults to inherit. Note that setting
this parameter might result in additional dependencies to be
added to the unit (see above). I<< Optional. Type uniline.  >> 

=head2 TTYPath

Sets the terminal device node to use if
standard input, output, or error are connected to a TTY (see
above). Defaults to
/dev/console. I<< Optional. Type uniline.  >> 

=head2 TTYReset

Reset the terminal device specified with
C<TTYPath> before and after execution.
Defaults to C<no>. I<< Optional. Type uniline.  >> 

=head2 TTYVHangup

Disconnect all clients which have opened the
terminal device specified with C<TTYPath>
before and after execution. Defaults to
C<no>. I<< Optional. Type uniline.  >> 

=head2 TTYVTDisallocate

If the terminal device specified with
C<TTYPath> is a virtual console terminal, try
to deallocate the TTY before and after execution. This ensures
that the screen and scrollback buffer is cleared. Defaults to
C<no>. I<< Optional. Type uniline.  >> 

=head2 SyslogIdentifier

Sets the process name to prefix log lines sent
to the logging system or the kernel log buffer with. If not
set, defaults to the process name of the executed process.
This option is only useful when
C<StandardOutput> or
C<StandardError> are set to
syslog, journal or
kmsg (or to the same settings in combination
with +console). I<< Optional. Type uniline.  >> 

=head2 SyslogFacility

Sets the syslog facility to use when logging
to syslog. One of kern,
user, mail,
daemon, auth,
syslog, lpr,
news, uucp,
cron, authpriv,
ftp, local0,
local1, local2,
local3, local4,
local5, local6 or
local7. See
L<syslog(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>syslog&C<sektion>3&C<manpath>Debian+unstable+sid">
for details. This option is only useful when
C<StandardOutput> or
C<StandardError> are set to
syslog. Defaults to
daemon. I<< Optional. Type uniline.  >> 

=head2 SyslogLevel

The default syslog level to use when logging to
syslog or the kernel log buffer. One of
emerg,
alert,
crit,
err,
warning,
notice,
info,
debug. See
L<syslog(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>syslog&C<sektion>3&C<manpath>Debian+unstable+sid">
for details. This option is only useful when
C<StandardOutput> or
C<StandardError> are set to
syslog or kmsg. Note that
individual lines output by the daemon might be prefixed with a
different log level which can be used to override the default
log level specified here. The interpretation of these prefixes
may be disabled with C<SyslogLevelPrefix>,
see below. For details, see
L<sd-daemon(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sd-daemon&C<sektion>3&C<manpath>Debian+unstable+sid">.
Defaults to
info. I<< Optional. Type uniline.  >> 

=head2 SyslogLevelPrefix

Takes a boolean argument. If true and
C<StandardOutput> or
C<StandardError> are set to
syslog, kmsg or
journal, log lines written by the executed
process that are prefixed with a log level will be passed on
to syslog with this log level set but the prefix removed. If
set to false, the interpretation of these prefixes is disabled
and the logged lines are passed on as-is. For details about
this prefixing see
L<sd-daemon(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sd-daemon&C<sektion>3&C<manpath>Debian+unstable+sid">.
Defaults to true. I<< Optional. Type boolean.  >> 

=head2 TimerSlackNSec

Sets the timer slack in nanoseconds for the
executed processes. The timer slack controls the accuracy of
wake-ups triggered by timers. See
L<prctl(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>prctl&C<sektion>2&C<manpath>Debian+unstable+sid">
for more information. Note that in contrast to most other time
span definitions this parameter takes an integer value in
nano-seconds if no unit is specified. The usual time units are
understood too. I<< Optional. Type uniline.  >> 

=head2 LimitCPU

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitFSIZE

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitDATA

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitSTACK

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitCORE

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitRSS

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitNOFILE

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitAS

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitNPROC

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitMEMLOCK

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitLOCKS

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitSIGPENDING

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitMSGQUEUE

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitNICE

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitRTPRIO

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 LimitRTTIME

These settings set both soft and hard limits
of various resources for executed processes. See
L<setrlimit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setrlimit&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Use the string infinity to
configure no limit on a specific resource. The multiplicative
suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E
may be used for resource limits measured in bytes
(e.g. C<LimitAS>16G). For the limits referring to time values,
the usual time units ms, s, min, h and so on may be used (see
L<systemd.time(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.time&C<sektion>7&C<manpath>Debian+unstable+sid">
for details). Note that if no time unit is specified for
C<LimitCPU> the default unit of seconds is
implied, while for C<LimitRTTIME> the default
unit of microseconds is implied. Also, note that the effective
granularity of the limits might influence their
enforcement. For example, time limits specified for
C<LimitCPU> will be rounded up implicitly to
multiples of 1s.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 C<LimitRSS> is not
implemented on Linux, and setting it has no effect. Often it
is advisable to prefer the resource controls listed in
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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,
C<MemoryLimit> is a more powerful (and
working) replacement for C<LimitRSS>.Limit directives and their equivalent with ulimitDirectiveulimit C<equivalentUnitLimitCPU>ulimit -C<tSecondsLimitFSIZE>ulimit -C<fBytesLimitDATA>ulimit -C<dBytesLimitSTACK>ulimit -C<sBytesLimitCORE>ulimit -C<cBytesLimitRSS>ulimit -C<mBytesLimitNOFILE>ulimit -nNumber of File C<DescriptorsLimitAS>ulimit -C<vBytesLimitNPROC>ulimit -uNumber of C<ProcessesLimitMEMLOCK>ulimit -C<lBytesLimitLOCKS>ulimit -xNumber of C<LocksLimitSIGPENDING>ulimit -iNumber of Queued C<SignalsLimitMSGQUEUE>ulimit -C<qBytesLimitNICE>ulimit -eNice C<LevelLimitRTPRIO>ulimit -rRealtime C<PriorityLimitRTTIME>No equivalentMicroseconds. I<< Optional. Type uniline.  >> 

=head2 PAMName

Sets the PAM service 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 C<User> setting. If
not set, no PAM session will be opened for the executed
processes. See
L<pam(8)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>pam&C<sektion>8&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type uniline.  >> 

=head2 CapabilityBoundingSet

Controls which capabilities to include in the
capability bounding set for the executed process. See
L<capabilities(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>capabilities&C<sektion>7&C<manpath>Debian+unstable+sid">
for details. Takes a whitespace-separated list of capability
names as read by
L<cap_from_name(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>cap_from_name&C<sektion>3&C<manpath>Debian+unstable+sid">,
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
C<~>, all but the listed capabilities will be
included, the effect of the assignment inverted. Note that
this option also affects the respective capabilities in the
effective, permitted and inheritable capability sets, on top
of what C<Capabilities> 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
process are enforced. This option may 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 the
empty capability set, and all prior settings have no effect.
If set to C<~> (without any further argument),
the bounding set is reset to the full set of available
capabilities, also undoing any previous
settings. I<< Optional. Type uniline.  >> 

=head2 SecureBits

Controls the secure bits set for the executed
process. Takes a space-separated combination of options from
the following list:
keep-caps,
keep-caps-locked,
no-setuid-fixup,
no-setuid-fixup-locked,
noroot, and
noroot-locked.
This 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 0. See
L<capabilities(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>capabilities&C<sektion>7&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type uniline.  >> 

=head2 Capabilities

Controls the
L<capabilities(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>capabilities&C<sektion>7&C<manpath>Debian+unstable+sid">
set for the executed process. Take a capability string
describing the effective, permitted and inherited capability
sets as documented in
L<cap_from_text(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>cap_from_text&C<sektion>3&C<manpath>Debian+unstable+sid">.
Note that these capability sets are usually influenced (and
filtered) by the capabilities attached to the executed file.
Due to that C<CapabilityBoundingSet> is
probably a much more useful setting. I<< Optional. Type uniline.  >> 

=head2 ReadWriteDirectories

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 hierarchy. Each
setting takes a space-separated list of absolute directory
paths. Directories listed in
C<ReadWriteDirectories> are accessible from
within the namespace with the same access rights as from
outside. Directories listed in
C<ReadOnlyDirectories> are accessible for
reading only, writing will be refused even if the usual file
access controls would permit this. Directories listed in
C<InaccessibleDirectories> will be made
inaccessible for processes inside the namespace. Note that
restricting access with these options does not extend to
submounts of a directory that are created later on. These
options may be specified more than once, in which case all
directories listed will have limited access from within the
namespace. If the empty string is assigned to this option, the
specific list is reset, and all prior assignments have no
effect.Paths in
C<ReadOnlyDirectories>
and
C<InaccessibleDirectories>
may be prefixed with
C<->, 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. I<< Optional. Type list of uniline.  >> 

=head2 ReadOnlyDirectories

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 hierarchy. Each
setting takes a space-separated list of absolute directory
paths. Directories listed in
C<ReadWriteDirectories> are accessible from
within the namespace with the same access rights as from
outside. Directories listed in
C<ReadOnlyDirectories> are accessible for
reading only, writing will be refused even if the usual file
access controls would permit this. Directories listed in
C<InaccessibleDirectories> will be made
inaccessible for processes inside the namespace. Note that
restricting access with these options does not extend to
submounts of a directory that are created later on. These
options may be specified more than once, in which case all
directories listed will have limited access from within the
namespace. If the empty string is assigned to this option, the
specific list is reset, and all prior assignments have no
effect.Paths in
C<ReadOnlyDirectories>
and
C<InaccessibleDirectories>
may be prefixed with
C<->, 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. I<< Optional. Type list of uniline.  >> 

=head2 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 hierarchy. Each
setting takes a space-separated list of absolute directory
paths. Directories listed in
C<ReadWriteDirectories> are accessible from
within the namespace with the same access rights as from
outside. Directories listed in
C<ReadOnlyDirectories> are accessible for
reading only, writing will be refused even if the usual file
access controls would permit this. Directories listed in
C<InaccessibleDirectories> will be made
inaccessible for processes inside the namespace. Note that
restricting access with these options does not extend to
submounts of a directory that are created later on. These
options may be specified more than once, in which case all
directories listed will have limited access from within the
namespace. If the empty string is assigned to this option, the
specific list is reset, and all prior assignments have no
effect.Paths in
C<ReadOnlyDirectories>
and
C<InaccessibleDirectories>
may be prefixed with
C<->, 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. I<< Optional. Type list of uniline.  >> 

=head2 PrivateTmp

Takes a boolean argument. If true, sets up a
new file system namespace for the executed processes and
mounts private /tmp and
/var/tmp directories inside it that is
not shared by processes outside of the namespace. This is
useful to secure access to temporary files of the process, but
makes sharing between processes via /tmp
or /var/tmp 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
C<JoinsNamespaceOf> directive, see
L<systemd.unit(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.unit&C<sektion>5&C<manpath>Debian+unstable+sid">
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. I<< Optional. Type boolean.  >> 

=head2 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
C<DevicePolicy>closed (see
L<systemd.resource-control(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.resource-control&C<sektion>5&C<manpath>Debian+unstable+sid">
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. I<< Optional. Type boolean.  >> 

=head2 PrivateNetwork

Takes a boolean argument. If true, sets up a
new network namespace for the executed processes and
configures only the loopback network device
C<lo> inside it. No other network devices will
be available to the executed process. This is useful to
securely turn off network access by the executed process.
Defaults to false. It is possible to run two or more units
within the same private network namespace by using the
C<JoinsNamespaceOf> directive, see
L<systemd.unit(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.unit&C<sektion>5&C<manpath>Debian+unstable+sid">
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). I<< Optional. Type boolean.  >> 

=head2 ProtectSystem

Takes a boolean argument or
C<full>. If true, mounts the
/usr and /boot
directories read-only for processes invoked by this unit. If
set to C<full>, the /etc
directory is mounted read-only, too. This setting ensures that
any modification of the vendor-supplied operating system (and
optionally its configuration) is prohibited for the service.
It is recommended to enable this setting for all long-running
services, unless they are involved with system updates or need
to modify the operating system in other ways. Note however
that processes retaining the CAP_SYS_ADMIN capability can undo
the effect of this setting. This setting is hence particularly
useful for daemons which have this capability removed, for
example with C<CapabilityBoundingSet>.
Defaults to off. I<< Optional. Type boolean.  >> 

=head2 ProtectHome

Takes a boolean argument or
C<read-only>. If true, the directories
/home, /root and
/run/user
are made inaccessible and empty for processes invoked by this
unit. If set to C<read-only>, the three
directories are made read-only instead. It is recommended to
enable this setting for all long-running services (in
particular network-facing ones), to ensure they cannot get
access to private user data, unless the services actually
require access to the user's private data. Note however that
processes retaining the CAP_SYS_ADMIN capability can undo the
effect of this setting. This setting is hence particularly
useful for daemons which have this capability removed, for
example with C<CapabilityBoundingSet>.
Defaults to off. I<< Optional. Type boolean.  >> 

=head2 MountFlags

Takes a mount propagation flag:
shared, slave or
private, which control whether mounts in the
file system namespace set up for this unit's processes will
receive or propagate mounts or unmounts. See
L<mount(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>mount&C<sektion>2&C<manpath>Debian+unstable+sid">
for details. Defaults to shared. Use
shared to ensure that mounts and unmounts are
propagated from the host to the container and vice versa. Use
slave to run processes so that none of their
mounts and unmounts will propagate to the host. Use
private to also ensure that no mounts and
unmounts from the host will propagate into the unit processes'
namespace. Note that slave means that file
systems mounted on the host might stay mounted continuously in
the unit's namespace, and thus keep the device busy. Note that
the file system namespace related options
(C<PrivateTmp>,
C<PrivateDevices>,
C<ProtectSystem>,
C<ProtectHome>,
C<ReadOnlyDirectories>,
C<InaccessibleDirectories> and
C<ReadWriteDirectories>) require that mount
and unmount propagation from the unit's file system namespace
is disabled, and hence downgrade shared to
slave. I<< Optional. Type uniline.  >> 

=head2 UtmpIdentifier

Takes a four character identifier string for
an L<utmp(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>utmp&C<sektion>5&C<manpath>Debian+unstable+sid">
and wtmp entry for this service. This should only be
set for services such as getty
implementations (such as L<agetty(8)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>agetty&C<sektion>8&C<manpath>Debian+unstable+sid">)
where utmp/wtmp entries must be created and cleared before and
after execution, or for services that shall be executed as if
they were run by a getty process (see
below). If the configured string is longer than four
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. I<< Optional. Type uniline.  >> 

=head2 UtmpMode

Takes one of C<init>,
C<login> or C<user>. If
C<UtmpIdentifier> is set, controls which
type of L<utmp(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>utmp&C<sektion>5&C<manpath>Debian+unstable+sid">/wtmp
entries for this service are generated. This setting has no
effect unless C<UtmpIdentifier> is set
too. If C<init> is set, only an
INIT_PROCESS entry is generated and the
invoked process must implement a
getty-compatible utmp/wtmp logic. If
C<login> is set, first an
INIT_PROCESS entry, followed by a
LOGIN_PROCESS entry is generated. In
this case, the invoked process must implement a L<login(1)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>login&C<sektion>1&C<manpath>Debian+unstable+sid">-compatible
utmp/wtmp logic. If C<user> is set, first an
INIT_PROCESS entry, then a
LOGIN_PROCESS entry and finally a
USER_PROCESS entry is generated. In this
case, the invoked process may be any process that is suitable
to be run as session leader. Defaults to
C<init>. I<< Optional. Type enum. choice: 'init', 'login', 'user'.  >> 

=head2 SELinuxContext

Set the SELinux security context of the
executed process. If set, this will override the automated
domain transition. However, the policy still needs to
authorize the transition. This directive is ignored if SELinux
is disabled. If prefixed by C<->, all errors
will be ignored. See
L<setexeccon(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>setexeccon&C<sektion>3&C<manpath>Debian+unstable+sid">
for details. I<< Optional. Type uniline.  >> 

=head2 AppArmorProfile

Takes a profile name as argument. The process
executed by the unit will switch to this profile when started.
Profiles must already be loaded in the kernel, or the unit
will fail. This result in a non operation if AppArmor is not
enabled. If prefixed by C<->, all errors will
be ignored. I<< Optional. Type uniline.  >> 

=head2 SmackProcessLabel

Takes a SMACK64 security
label as argument. The process executed by the unit will be
started under this label and SMACK will decide whether the
process is allowed to run or not, based on it. The process
will continue to run under the label specified here unless the
executable has its own SMACK64EXEC label, in
which case the process will transition to run under that
label. When not specified, the label that systemd is running
under is used. This directive is ignored if SMACK is
disabled.The value may be prefixed by C<->, in
which case all errors will be ignored. An empty value may be
specified to unset previous assignments. I<< Optional. Type uniline.  >> 

=head2 IgnoreSIGPIPE

Takes a boolean argument. If true, causes
SIGPIPE to be ignored in the executed
process. Defaults to true because SIGPIPE
generally is useful only in shell pipelines. I<< Optional. Type boolean.  >> 

=head2 NoNewPrivileges

Takes a boolean 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 secure bits flags (see above), as it also prohibits
UID changes of any kind. This is the simplest, most effective
way to ensure that a process and its children can never
elevate privileges again. I<< Optional. Type boolean.  >> 

=head2 SystemCallFilter

Takes a space-separated list of system call
names. If this setting is used, all system calls executed by
the unit processes except for the listed ones will result in
immediate process termination with the
SIGSYS signal (whitelisting). If the
first character of the list is C<~>, the
effect is inverted: only the listed system calls will result
in immediate process termination (blacklisting). If running in
user mode and this option is used,
C<NoNewPrivileges>yes is implied. This
feature makes use of the Secure Computing Mode 2 interfaces of
the kernel ('seccomp filtering') and is useful for enforcing a
minimal sandboxing environment. Note that the
execve,
rt_sigreturn,
sigreturn,
exit_group, exit
system calls 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 prior assignments will
have no effect.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.) I<< Optional. Type list of uniline.  >> 

=head2 SystemCallErrorNumber

Takes an C<errno> error number
name to return when the system call filter configured with
C<SystemCallFilter> is triggered, instead of
terminating the process immediately. Takes an error name such
as EPERM, EACCES or
EUCLEAN. When this setting is not used,
or when the empty string is assigned, the process will be
terminated immediately when the filter is
triggered. I<< Optional. Type uniline.  >> 

=head2 SystemCallArchitectures

Takes a space-separated list of architecture
identifiers to include in the system call filter. The known
architecture identifiers are x86,
x86-64, x32,
arm as well as the special identifier
native. Only system calls of the
specified architectures will be permitted to processes of this
unit. This is an effective way to disable compatibility with
non-native architectures for processes, for example to
prohibit execution of 32-bit x86 binaries on 64-bit x86-64
systems. The special native identifier
implicitly maps to the native architecture of the system (or
more strictly: to the architecture the system manager is
compiled for). If running in user mode and this option is
used, C<NoNewPrivileges>yes is implied. Note
that setting this option to a non-empty list implies that
native is included too. By default, this
option is set to the empty list, i.e. no architecture system
call filtering is applied. I<< Optional. Type uniline.  >> 

=head2 RestrictAddressFamilies

Restricts the set of socket address families
accessible to the processes of this unit. Takes a
space-separated list of address family names to whitelist,
such as
AF_UNIX,
AF_INET or
AF_INET6. When
prefixed with ~ the listed address
families will be applied as blacklist, otherwise as whitelist.
Note that this restricts access to the
L<socket(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>socket&C<sektion>2&C<manpath>Debian+unstable+sid">
system call only. Sockets passed into the process by other
means (for example, by using socket activation with socket
units, see
L<systemd.socket(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.socket&C<sektion>5&C<manpath>Debian+unstable+sid">)
are unaffected. Also, sockets created with
socketpair() (which creates connected
AF_UNIX sockets only) are unaffected. Note that this option
has no effect on 32-bit x86 and is ignored (but works
correctly on x86-64). If running in user mode and this option
is used, C<NoNewPrivileges>yes is implied. By
default, no restriction applies, all address families are
accessible to processes. If assigned the empty string, any
previous list changes are undone.Use this option to limit exposure of processes to remote
systems, in particular via exotic network protocols. Note that
in most cases, the local AF_UNIX address
family should be included in the configured whitelist as it is
frequently used for local communication, including for
L<syslog(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>syslog&C<sektion>2&C<manpath>Debian+unstable+sid">
logging. I<< Optional. Type uniline.  >> 

=head2 Personality

Controls which kernel architecture
L<uname(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>uname&C<sektion>2&C<manpath>Debian+unstable+sid">
shall report, when invoked by unit processes. Takes one of
x86 and x86-64. This
is useful when running 32-bit services on a 64-bit host
system. If not specified, the personality is left unmodified
and thus reflects the personality of the host system's
kernel. I<< Optional. Type enum. choice: 'x86', 'x86-64'.  >> 

=head2 RuntimeDirectory

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
C<RuntimeDirectoryMode>, and will be owned by
the user and group specified in C<User> and
C<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 C</>, i.e.
must refer to simple directories to create or remove. This is
particularly useful for unprivileged 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
L<tmpfiles.d(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>tmpfiles.d&C<sektion>5&C<manpath>Debian+unstable+sid">. I<< Optional. Type uniline.  >> 

=head2 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
C<RuntimeDirectoryMode>, and will be owned by
the user and group specified in C<User> and
C<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 C</>, i.e.
must refer to simple directories to create or remove. This is
particularly useful for unprivileged 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
L<tmpfiles.d(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>tmpfiles.d&C<sektion>5&C<manpath>Debian+unstable+sid">. I<< Optional. Type uniline.  >> 

=head2 KillMode

Specifies how processes of this unit shall be
killed. One of
control-group,
process,
mixed,
none.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 C<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 C<KillSignal>). Optionally, this
is immediately followed by a SIGHUP (if
enabled with C<SendSIGHUP>). If then, after a
delay (configured via the C<TimeoutStopSec>
option), processes still remain, the termination request is
repeated with the SIGKILL signal (unless
this is disabled via the C<SendSIGKILL>
option). See
L<kill(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>kill&C<sektion>2&C<manpath>Debian+unstable+sid">
for more information.Defaults to
control-group. I<< Optional. Type uniline.  >> 

=head2 KillSignal

Specifies which signal to use when killing a
service. This controls the signal that is sent as first step
of shutting down a unit (see above), and is usually followed
by SIGKILL (see above and below). For a
list of valid signals, see
L<signal(7)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>signal&C<sektion>7&C<manpath>Debian+unstable+sid">.
Defaults to SIGTERM. 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. I<< Optional. Type uniline.  >> 

=head2 SendSIGHUP

Specifies whether to send
SIGHUP to remaining processes immediately
after sending the signal configured with
C<KillSignal>. This is useful to indicate to
shells and shell-like programs that their connection has been
severed. Takes a boolean value. Defaults to "no".
I<< Optional. Type boolean.  >> 

=head2 SendSIGKILL

Specifies whether to send
SIGKILL to remaining processes after a
timeout, if the normal shutdown procedure left processes of
the service around. Takes a boolean value. Defaults to "yes".
I<< Optional. Type boolean.  >> 

=head2 Type

Configures the process start-up type for this
service unit. One of
simple,
forking,
oneshot,
dbus,
notify or
idle.If set to simple (the default if
neither C<Type> nor
C<BusName>, but C<ExecStart>
are specified), it is expected that the process configured
with C<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 C<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 C<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.
C<RemainAfterExit> is particularly useful for
this type of service. This is the implied default if neither
C<Type> or C<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
C<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 C<BusName>
is specified.Behavior of notify is similar to
simple; however, it is expected that the
daemon sends a notification message via
L<sd_notify(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sd_notify&C<sektion>3&C<manpath>Debian+unstable+sid">
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,
C<NotifyAccess> (see below) should be set to
open access to the notification socket provided by systemd. If
C<NotifyAccess> is not set, it will be
implicitly set to main. Note that currently
C<Type>notify will not work
if used in combination with
C<PrivateNetwork>yes.Behavior of idle is very similar to
simple; however, actual execution of the
service binary is delayed until all jobs are dispatched. This
may be used to avoid interleaving of output of shell services
with the status output on the console. I<< Optional. Type uniline.  >> 

=head2 RemainAfterExit

Takes a boolean value that specifies whether
the service shall be considered active even when all its
processes exited. Defaults to no. I<< Optional. Type boolean.  >> 

=head2 GuessMainPID

Takes a boolean value that specifies whether
systemd should try to guess the main PID of a service if it
cannot be determined reliably. This option is ignored unless
C<Type>forking is set and
C<PIDFile> is unset because for the other types
or with an explicitly configured PID file, the main PID is
always known. The guessing algorithm might come to incorrect
conclusions if a daemon consists of more than one process. If
the main PID cannot be determined, failure detection and
automatic restarting of a service will not work reliably.
Defaults to yes. I<< Optional. Type boolean.  >> 

=head2 PIDFile

Takes an absolute file name pointing to the
PID file of this daemon. Use of this option is recommended for
services where C<Type> is set to
forking. systemd will read the PID of the
main process of the daemon after start-up of the service.
systemd will not write to the file configured here, although
it will remove the file after the service has shut down if it
still exists.
I<< Optional. Type uniline.  >> 

=head2 BusName

Takes a D-Bus bus name that this service is
reachable as. This option is mandatory for services where
C<Type> is set to
dbus. I<< Optional. Type uniline.  >> 

=head2 BusPolicy

If specified, a custom kdbus
endpoint will be created and installed as the default bus node
for the service. Such a custom endpoint can hold an own set of
policy rules that are enforced on top of the bus-wide ones.
The custom endpoint is named after the service it was created
for, and its node will be bind-mounted over the default bus
node location, so the service can only access the bus through
its own endpoint. Note that custom bus endpoints default to a
"deny all" policy. Hence, if at least one
C<BusPolicy> directive is given, you have to
make sure to add explicit rules for everything the service
should be able to do.The value of this directive is comprised
of two parts; the bus name, and a verb to
specify to granted access, which is one of
see,
talk, or
own.
talk implies
see, and own
implies both talk and
see.
If multiple access levels are specified for the
same bus name, the most powerful one takes
effect.
Examples:C<BusPolicy>org.freedesktop.systemd1 C<talkBusPolicy>org.foo.bar seeThis option is only available on kdbus enabled systems. I<< Optional. Type uniline.  >> 

=head2 ExecStart

Commands with their arguments that are
executed when this service is started. The value is split into
zero or more command lines according to the rules described
below (see section "Command Lines" below).
When C<Type> is not
oneshot, only one command may and must be
given. When C<Type>oneshot is used, zero or
more commands may be specified. This can 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
C<ExecStart> is specified, then the service
must have C<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 C<@>, the second
token will be passed as C<argv[0]> to the
executed process, followed by the further arguments specified.
If the absolute filename is prefixed with
C<->, 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 both
C<-> and C<@> are used, they
can appear in either 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
C<->), other lines are not executed, and the
unit is considered failed.Unless C<Type>forking is set, the
process started via this command line will be considered the
main process of the daemon. I<< Optional. Type list of uniline.  >> 

=head2 ExecStartPre

Additional commands that are executed before
or after the command in C<ExecStart>,
respectively. Syntax is the same as for
C<ExecStart>, except that multiple command
lines are allowed and the commands are executed one after the
other, serially.If any of those commands (not prefixed with
C<->) fail, the rest are not executed and the
unit is considered failed.C<ExecStart> commands are only run after
all C<ExecStartPre> commands that were not prefixed
with a C<-> exit successfully.C<ExecStartPost> commands are only run after
the service has started, as determined by C<Type>
(i.e. the process has been started for C<Type>simple
or C<Type>idle, the process exits successfully for
C<Type>oneshot, the initial process exits successfully
for C<Type>forking, C<C<READY>1> is sent
for C<Type>notify, or the C<BusName>
has been taken for C<Type>dbus).Note that C<ExecStartPre> may not be
used to start long-running processes. All processes forked
off by processes invoked via C<ExecStartPre> will
be killed before the next service process is run. I<< Optional. Type list of uniline.  >> 

=head2 ExecStartPost

Additional commands that are executed before
or after the command in C<ExecStart>,
respectively. Syntax is the same as for
C<ExecStart>, except that multiple command
lines are allowed and the commands are executed one after the
other, serially.If any of those commands (not prefixed with
C<->) fail, the rest are not executed and the
unit is considered failed.C<ExecStart> commands are only run after
all C<ExecStartPre> commands that were not prefixed
with a C<-> exit successfully.C<ExecStartPost> commands are only run after
the service has started, as determined by C<Type>
(i.e. the process has been started for C<Type>simple
or C<Type>idle, the process exits successfully for
C<Type>oneshot, the initial process exits successfully
for C<Type>forking, C<C<READY>1> is sent
for C<Type>notify, or the C<BusName>
has been taken for C<Type>dbus).Note that C<ExecStartPre> may not be
used to start long-running processes. All processes forked
off by processes invoked via C<ExecStartPre> will
be killed before the next service process is run. I<< Optional. Type list of uniline.  >> 

=head2 ExecReload

Commands to execute to trigger a configuration
reload in the service. This argument takes multiple command
lines, following the same scheme as described for
C<ExecStart> above. Use of this setting is
optional. Specifier and environment variable substitution is
supported here following the same scheme as for
C<ExecStart>.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:/bin/kill -HUP $MAINPIDNote 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
C<ExecReload> to a command that not only
triggers a configuration reload of the daemon, but also
synchronously waits for it to complete. I<< Optional. Type list of uniline.  >> 

=head2 ExecStop

Commands to execute to stop the service
started via C<ExecStart>. This argument takes
multiple command lines, following the same scheme as described
for C<ExecStart> above. Use of this setting
is optional. After the commands configured in this option are
run, all processes remaining for a service are terminated
according to the C<KillMode> setting (see
L<systemd.kill(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.kill&C<sektion>5&C<manpath>Debian+unstable+sid">).
If this option is not specified, the process is terminated by
sending the signal specified in C<KillSignal>
when service stop is requested. Specifier and environment
variable substitution is supported (including
$MAINPID, see above).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. I<< Optional. Type list of uniline.  >> 

=head2 ExecStopPost

Additional commands that are executed after
the service was stopped. This includes cases where the
commands configured in C<ExecStop> were used,
where the service does not have any
C<ExecStop> defined, or where the service
exited unexpectedly. This argument takes multiple command
lines, following the same scheme as described for
C<ExecStart>. Use of these settings is
optional. Specifier and environment variable substitution is
supported. I<< Optional. Type list of uniline.  >> 

=head2 RestartSec

Configures the time to sleep before restarting
a service (as configured with C<Restart>).
Takes a unit-less value in seconds, or a time span value such
as "5min 20s". Defaults to 100ms. I<< Optional. Type uniline.  >> 

=head2 TimeoutStartSec

Configures the time to wait for start-up. If a
daemon service does not signal start-up completion within the
configured time, the service will be considered failed and
will be shut down again. Takes a unit-less value in seconds,
or a time span value such as "5min 20s". Pass
C<0> to disable the timeout logic. Defaults to
C<DefaultTimeoutStartSec> from the manager
configuration file, except when
C<Type>oneshot is used, in which case the
timeout is disabled by default (see
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">).
I<< Optional. Type uniline.  >> 

=head2 TimeoutStopSec

Configures the time to wait for stop. If a
service is asked to stop, but does not terminate in the
specified time, it will be terminated forcibly via
SIGTERM, and after another timeout of
equal duration with SIGKILL (see
C<KillMode> in
L<systemd.kill(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.kill&C<sektion>5&C<manpath>Debian+unstable+sid">).
Takes a unit-less value in seconds, or a time span value such
as "5min 20s". Pass C<0> to disable the
timeout logic. Defaults to
C<DefaultTimeoutStopSec> from the manager
configuration file (see
L<systemd-system.conf(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd-system.conf&C<sektion>5&C<manpath>Debian+unstable+sid">).
I<< Optional. Type uniline.  >> 

=head2 TimeoutSec

A shorthand for configuring both
C<TimeoutStartSec> and
C<TimeoutStopSec> to the specified value.
I<< Optional. Type uniline.  >> 

=head2 WatchdogSec

Configures the watchdog timeout for a service.
The watchdog is activated when the start-up is completed. The
service must call
L<sd_notify(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sd_notify&C<sektion>3&C<manpath>Debian+unstable+sid">
regularly with C<C<WATCHDOG>1> (i.e. the
"keep-alive ping"). If the time between two such calls is
larger than the configured time, then the service is placed in
a failed state and it will be terminated with
SIGABRT. By setting
C<Restart> to on-failure or
always, the service will be automatically
restarted. The time configured here will be passed to the
executed service process in the
C<WATCHDOG_USEC> environment variable. This
allows daemons to automatically enable the keep-alive pinging
logic if watchdog support is enabled for the service. If this
option is used, C<NotifyAccess> (see below)
should be set to open access to the notification socket
provided by systemd. If C<NotifyAccess> is
not set, it will be implicitly set to main.
Defaults to 0, which disables this feature. The service can
check whether the service manager expects watchdog keep-alive
notifications. See
L<sd_watchdog_enabled(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sd_watchdog_enabled&C<sektion>3&C<manpath>Debian+unstable+sid">
for details.
I<< Optional. Type uniline.  >> 

=head2 Restart

Configures whether the service shall be
restarted when the service process exits, is killed, or a
timeout is reached. The service process may be the main
service process, but it may also be one of the processes
specified with C<ExecStartPre>,
C<ExecStartPost>,
C<ExecStop>,
C<ExecStopPost>, or
C<ExecReload>. When the death of the process
is a result of systemd operation (e.g. service stop or
restart), the service will not be restarted. Timeouts include
missing the watchdog "keep-alive ping" deadline and a service
start, reload, and stop operation timeouts.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
C<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.Exit causes and the effect of the C<Restart> settings on themRestart settings/Exit causesnoalwayson-successon-failureon-abnormalon-aborton-watchdogClean exit code or signalXXUnclean exit codeXXUnclean signalXXXXTimeoutXXXWatchdogXXXXAs exceptions to the setting above, the service will not
be restarted if the exit code or signal is specified in
C<RestartPreventExitStatus> (see below).
Also, the services will always be restarted if the exit code
or signal is specified in
C<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. I<< Optional. Type enum. choice: 'no', 'on-success', 'on-failure', 'on-abnormal', 'on-watchdog', 'on-abort', 'always'.  >> 

=head2 SuccessExitStatus

Takes a list of exit status definitions that,
when returned by the main service process, will be considered
successful termination, in addition to the normal successful
exit code 0 and the signals SIGHUP,
SIGINT, SIGTERM, and
SIGPIPE. Exit status definitions can
either be numeric exit codes or termination signal names,
separated by spaces. For example:
C<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
L<_exit(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>_exit&C<sektion>2&C<manpath>Debian+unstable+sid">
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 -- 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. I<< Optional. Type uniline.  >> 

=head2 RestartPreventExitStatus

Takes a list of exit status definitions that,
when returned by the main service process, will prevent
automatic service restarts, regardless of the restart setting
configured with C<Restart>. Exit status
definitions can either be numeric exit codes or termination
signal names, and are separated by spaces. Defaults to the
empty list, so that, by default, no exit status is excluded
from the configured restart logic. For example:
C<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. I<< Optional. Type uniline.  >> 

=head2 RestartForceExitStatus

Takes a list of exit status definitions that,
when returned by the main service process, will force automatic
service restarts, regardless of the restart setting configured
with C<Restart>. The argument format is
similar to
C<RestartPreventExitStatus>. I<< Optional. Type uniline.  >> 

=head2 PermissionsStartOnly

Takes a boolean argument. If true, the
permission-related execution options, as configured with
C<User> and similar options (see
L<systemd.exec(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.exec&C<sektion>5&C<manpath>Debian+unstable+sid">
for more information), are only applied to the process started
with
C<ExecStart>, and not to the various other
C<ExecStartPre>,
C<ExecStartPost>,
C<ExecReload>,
C<ExecStop>, and
C<ExecStopPost>
commands. If false, the setting is applied to all configured
commands the same way. Defaults to false. I<< Optional. Type boolean.  >> 

=head2 RootDirectoryStartOnly

Takes a boolean argument. If true, the root
directory, as configured with the
C<RootDirectory> option (see
L<systemd.exec(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.exec&C<sektion>5&C<manpath>Debian+unstable+sid">
for more information), is only applied to the process started
with C<ExecStart>, and not to the various
other C<ExecStartPre>,
C<ExecStartPost>,
C<ExecReload>, C<ExecStop>,
and C<ExecStopPost> commands. If false, the
setting is applied to all configured commands the same way.
Defaults to false. I<< Optional. Type boolean.  >> 

=head2 NonBlocking

Set the O_NONBLOCK flag
for all file descriptors passed via socket-based activation.
If true, all file descriptors >= 3 (i.e. all except stdin,
stdout, and stderr) will have the
O_NONBLOCK flag set and hence are in
non-blocking mode. This option is only useful in conjunction
with a socket unit, as described in
L<systemd.socket(5)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>systemd.socket&C<sektion>5&C<manpath>Debian+unstable+sid">.
Defaults to false. I<< Optional. Type uniline.  >> 

=head2 NotifyAccess

Controls access to the service status
notification socket, as accessible via the
L<sd_notify(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sd_notify&C<sektion>3&C<manpath>Debian+unstable+sid">
call. Takes one of none (the default),
main or all. If
none, no daemon status updates are accepted
from the service processes, all status update messages are
ignored. If main, only service updates sent
from the main process of the service are accepted. If
all, all services updates from all members of
the service's control group are accepted. This option should
be set to open access to the notification socket when using
C<Type>notify or
C<WatchdogSec> (see above). If those options
are used but C<NotifyAccess> is not
configured, it will be implicitly set to
main. I<< Optional. Type enum. choice: 'none', 'main', 'all'.  >> 

=head2 Sockets

Specifies the name of the socket units this
service shall inherit socket file descriptors from when the
service is started. Normally, it should not be necessary to use
this setting, as all socket file descriptors whose unit shares
the same name as the service (subject to the different unit
name suffix of course) are passed to the spawned
process.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
C<Service> setting of
.socket units does not have to match the
inverse of the C<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. I<< Optional. Type uniline.  >> 

=head2 StartLimitInterval

Configure service start rate limiting. By
default, services which are started more than 5 times within
10 seconds are not permitted to start any more times until the
10 second interval ends. With these two options, this rate
limiting may be modified. Use
C<StartLimitInterval> to configure the
checking interval (defaults to
C<DefaultStartLimitInterval> in manager
configuration file, set to 0 to disable any kind of rate
limiting). Use C<StartLimitBurst> to
configure how many starts per interval are allowed (defaults
to C<DefaultStartLimitBurst> in manager
configuration file). These configuration options are
particularly useful in conjunction with
C<Restart>; however, they apply to all kinds
of starts (including manual), not just those triggered by the
C<Restart> logic. Note that units which are
configured for C<Restart> and which reach the
start limit are not attempted to be restarted anymore;
however, they may still be restarted manually at a later
point, from which point on, the restart logic is again
activated. Note that systemctl reset-failed
will cause the restart rate counter for a service to be
flushed, which is useful if the administrator wants to
manually start a service and the start limit interferes with
that. I<< Optional. Type uniline.  >> 

=head2 StartLimitBurst

Configure service start rate limiting. By
default, services which are started more than 5 times within
10 seconds are not permitted to start any more times until the
10 second interval ends. With these two options, this rate
limiting may be modified. Use
C<StartLimitInterval> to configure the
checking interval (defaults to
C<DefaultStartLimitInterval> in manager
configuration file, set to 0 to disable any kind of rate
limiting). Use C<StartLimitBurst> to
configure how many starts per interval are allowed (defaults
to C<DefaultStartLimitBurst> in manager
configuration file). These configuration options are
particularly useful in conjunction with
C<Restart>; however, they apply to all kinds
of starts (including manual), not just those triggered by the
C<Restart> logic. Note that units which are
configured for C<Restart> and which reach the
start limit are not attempted to be restarted anymore;
however, they may still be restarted manually at a later
point, from which point on, the restart logic is again
activated. Note that systemctl reset-failed
will cause the restart rate counter for a service to be
flushed, which is useful if the administrator wants to
manually start a service and the start limit interferes with
that. I<< Optional. Type uniline.  >> 

=head2 StartLimitAction

Configure the action to take if the rate limit
configured with C<StartLimitInterval> and
C<StartLimitBurst> is hit. Takes one of
none,
reboot,
reboot-force,
reboot-immediate,
poweroff,
poweroff-force or
poweroff-immediate. If
none is set, hitting the rate limit will
trigger no action besides that the start will not be
permitted. reboot causes a reboot following
the normal shutdown procedure (i.e. equivalent to
systemctl reboot).
reboot-force causes a forced reboot which
will terminate all processes forcibly but should cause no
dirty file systems on reboot (i.e. equivalent to
systemctl reboot -f) and
reboot-immediate causes immediate execution
of the
L<reboot(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>reboot&C<sektion>2&C<manpath>Debian+unstable+sid">
system call, which might result in data loss. Similarly,
poweroff, poweroff-force,
poweroff-immediate have the effect of
powering down the system with similar semantics. Defaults to
none. I<< Optional. Type enum. choice: 'none', 'reboot', 'reboot-force', 'reboot-immediate', 'poweroff', 'poweroff-force', 'poweroff-immediate'.  >> 

=head2 FailureAction

Configure the action to take when the service
enters a failed state. Takes the same values as
C<StartLimitAction> and executes the same
actions. Defaults to none. I<< Optional. Type uniline.  >> 

=head2 RebootArgument

Configure the optional argument for the
L<reboot(2)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>reboot&C<sektion>2&C<manpath>Debian+unstable+sid">
system call if C<StartLimitAction> or
C<FailureAction> is a reboot action. This
works just like the optional argument to systemctl
reboot command. I<< Optional. Type uniline.  >> 

=head2 FileDescriptorStoreMax

Configure how many file descriptors may be
stored in the service manager for the service using
L<sd_pid_notify_with_fds(3)|"https://manpages.debian.org/cgi-bin/man.cgi?C<query>sd_pid_notify_with_fds&C<sektion>3&C<manpath>Debian+unstable+sid">'s
C<C<FDSTORE>1> messages. This is useful for
implementing service restart schemes where the state is
serialized to /run and the file
descriptors passed to the service manager, to allow restarts
without losing state. Defaults to 0, i.e. no file descriptors
may be stored in the service manager by default. All file
descriptors passed to the service manager from a specific
service are passed back to the service's main process on the
next service restart. Any file descriptors passed to the
service manager are automatically closed when POLLHUP or
POLLERR is seen on them, or when the service is fully stopped
and no job queued or being executed for it. I<< Optional. Type uniline.  >> 

=head2 USBFunctionDescriptors

Configure the location of a file containing
USB
FunctionFS descriptors, for implementation of USB
gadget functions. This is used only in conjunction with a
socket unit with C<ListenUSBFunction>
configured. The contents of this file are written to the
ep0 file after it is
opened. I<< Optional. Type uniline.  >> 

=head2 USBFunctionStrings

Configure the location of a file containing
USB FunctionFS strings.  Behavior is similar to
C<USBFunctionDescriptors>
above. I<< Optional. Type uniline.  >> 

=head1 SEE ALSO

=over

=item *

L<cme>

=back

=head1 COPYRIGHT

=over

=item 2010-2016 Lennart Poettering and others

=item 2016 Dominique Dumont


=back

=head1 LICENSE

=over

=item LGPLv2.1+


=back

=cut

