2018-07-03 05:15:39 +08:00
|
|
|
<?xml version='1.0'?>
|
2019-03-14 21:40:58 +08:00
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
2018-02-15 18:43:08 +08:00
|
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
|
|
|
|
|
<!ENTITY % entities SYSTEM "custom-entities.ent" >
|
|
|
|
|
%entities;
|
|
|
|
|
]>
|
2020-11-09 12:23:58 +08:00
|
|
|
<!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
|
2010-07-07 07:38:56 +08:00
|
|
|
|
2014-11-29 17:06:04 +08:00
|
|
|
<refentry id="systemd-system.conf"
|
2015-02-04 10:14:13 +08:00
|
|
|
xmlns:xi="http://www.w3.org/2001/XInclude">
|
|
|
|
|
<refentryinfo>
|
|
|
|
|
<title>systemd-system.conf</title>
|
|
|
|
|
<productname>systemd</productname>
|
|
|
|
|
</refentryinfo>
|
|
|
|
|
|
|
|
|
|
<refmeta>
|
|
|
|
|
<refentrytitle>systemd-system.conf</refentrytitle>
|
|
|
|
|
<manvolnum>5</manvolnum>
|
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
|
<refname>systemd-system.conf</refname>
|
|
|
|
|
<refname>system.conf.d</refname>
|
|
|
|
|
<refname>systemd-user.conf</refname>
|
|
|
|
|
<refname>user.conf.d</refname>
|
|
|
|
|
<refpurpose>System and session service manager configuration files</refpurpose>
|
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
2015-09-10 18:32:16 +08:00
|
|
|
<para><filename>/etc/systemd/system.conf</filename>,
|
|
|
|
|
<filename>/etc/systemd/system.conf.d/*.conf</filename>,
|
|
|
|
|
<filename>/run/systemd/system.conf.d/*.conf</filename>,
|
|
|
|
|
<filename>/usr/lib/systemd/system.conf.d/*.conf</filename></para>
|
2021-02-19 17:56:04 +08:00
|
|
|
|
|
|
|
|
<para><filename>~/.config/systemd/user.conf</filename>,
|
|
|
|
|
<filename>/etc/systemd/user.conf</filename>,
|
2015-09-10 18:32:16 +08:00
|
|
|
<filename>/etc/systemd/user.conf.d/*.conf</filename>,
|
|
|
|
|
<filename>/run/systemd/user.conf.d/*.conf</filename>,
|
|
|
|
|
<filename>/usr/lib/systemd/user.conf.d/*.conf</filename></para>
|
2015-02-04 10:14:13 +08:00
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
2021-02-19 17:56:04 +08:00
|
|
|
<para>When run as a system instance, <command>systemd</command> interprets the configuration file
|
|
|
|
|
<filename>system.conf</filename> and the files in <filename>system.conf.d</filename> directories; when
|
|
|
|
|
run as a user instance, it interprets the configuration file <filename>user.conf</filename> (either in
|
|
|
|
|
the home directory of the user, or if not found, under <filename>/etc/systemd/</filename>) and the files
|
|
|
|
|
in <filename>user.conf.d</filename> directories. These configuration files contain a few settings
|
|
|
|
|
controlling basic manager operations.</para>
|
|
|
|
|
|
|
|
|
|
<para>See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.syntax</refentrytitle><manvolnum>7</manvolnum></citerefentry> for a
|
|
|
|
|
general description of the syntax.</para>
|
2015-02-04 10:14:13 +08:00
|
|
|
</refsect1>
|
|
|
|
|
|
2015-03-04 08:10:21 +08:00
|
|
|
<xi:include href="standard-conf.xml" xpointer="main-conf" />
|
2015-02-04 10:14:13 +08:00
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Options</title>
|
|
|
|
|
|
|
|
|
|
<para>All options are configured in the
|
2020-07-06 17:00:06 +08:00
|
|
|
[Manager] section:</para>
|
2015-02-04 10:14:13 +08:00
|
|
|
|
2019-02-13 17:49:47 +08:00
|
|
|
<variablelist class='config-directives'>
|
2015-02-04 10:14:13 +08:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>LogColor=</varname></term>
|
2020-01-17 22:47:30 +08:00
|
|
|
<term><varname>LogLevel=</varname></term>
|
2015-02-04 10:14:13 +08:00
|
|
|
<term><varname>LogLocation=</varname></term>
|
2020-01-17 22:47:30 +08:00
|
|
|
<term><varname>LogTarget=</varname></term>
|
2019-07-15 21:56:24 +08:00
|
|
|
<term><varname>LogTime=</varname></term>
|
2015-02-04 10:14:13 +08:00
|
|
|
<term><varname>DumpCore=yes</varname></term>
|
2015-09-24 05:13:06 +08:00
|
|
|
<term><varname>CrashChangeVT=no</varname></term>
|
2015-02-04 10:14:13 +08:00
|
|
|
<term><varname>CrashShell=no</varname></term>
|
2015-09-24 05:13:06 +08:00
|
|
|
<term><varname>CrashReboot=no</varname></term>
|
2015-02-04 10:14:13 +08:00
|
|
|
<term><varname>ShowStatus=yes</varname></term>
|
|
|
|
|
<term><varname>DefaultStandardOutput=journal</varname></term>
|
|
|
|
|
<term><varname>DefaultStandardError=inherit</varname></term>
|
|
|
|
|
|
2016-12-21 04:15:17 +08:00
|
|
|
<listitem><para>Configures various parameters of basic manager operation. These options may be overridden by
|
|
|
|
|
the respective process and kernel command line arguments. See
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
|
|
|
|
|
details.</para></listitem>
|
2015-02-04 10:14:13 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2016-10-07 09:08:21 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>CtrlAltDelBurstAction=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Defines what action will be performed
|
2016-10-13 05:02:44 +08:00
|
|
|
if user presses Ctrl-Alt-Delete more than 7 times in 2s.
|
2016-10-18 18:16:32 +08:00
|
|
|
Can be set to <literal>reboot-force</literal>, <literal>poweroff-force</literal>,
|
|
|
|
|
<literal>reboot-immediate</literal>, <literal>poweroff-immediate</literal>
|
|
|
|
|
or disabled with <literal>none</literal>. Defaults to
|
2016-10-07 09:08:21 +08:00
|
|
|
<literal>reboot-force</literal>.
|
|
|
|
|
</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 10:14:13 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>CPUAffinity=</varname></term>
|
|
|
|
|
|
2019-05-24 14:35:51 +08:00
|
|
|
<listitem><para>Configures the CPU affinity for the service manager as well as the default CPU
|
|
|
|
|
affinity for all forked off 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. Individual services may override the CPU affinity for their processes with the
|
|
|
|
|
<varname>CPUAffinity=</varname> setting in unit files, see
|
2018-07-23 17:05:40 +08:00
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
2019-03-13 01:58:26 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>NUMAPolicy=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configures the NUMA memory policy for the service manager and the default NUMA memory policy
|
|
|
|
|
for all forked off processes. Individual services may override the default policy with the
|
|
|
|
|
<varname>NUMAPolicy=</varname> setting in unit files, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>NUMAMask=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configures the NUMA node mask that will be associated with the selected NUMA policy. Note that
|
|
|
|
|
<option>default</option> and <option>local</option> NUMA policies don't require explicit NUMA node mask and
|
2019-06-27 15:54:20 +08:00
|
|
|
value of the option can be empty. Similarly to <varname>NUMAPolicy=</varname>, value can be overridden
|
2019-03-13 01:58:26 +08:00
|
|
|
by individual services in unit files, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
2015-02-04 10:14:13 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>RuntimeWatchdogSec=</varname></term>
|
2019-07-22 18:39:25 +08:00
|
|
|
<term><varname>RebootWatchdogSec=</varname></term>
|
2019-07-19 18:54:15 +08:00
|
|
|
<term><varname>KExecWatchdogSec=</varname></term>
|
2015-02-04 10:14:13 +08:00
|
|
|
|
2018-03-22 05:00:21 +08:00
|
|
|
<listitem><para>Configure the hardware watchdog at runtime and at reboot. Takes a timeout value in seconds (or
|
|
|
|
|
in other time units if suffixed with <literal>ms</literal>, <literal>min</literal>, <literal>h</literal>,
|
|
|
|
|
<literal>d</literal>, <literal>w</literal>). If <varname>RuntimeWatchdogSec=</varname> is set to a non-zero
|
|
|
|
|
value, the watchdog hardware (<filename>/dev/watchdog</filename> or the path specified with
|
|
|
|
|
<varname>WatchdogDevice=</varname> or the kernel option <varname>systemd.watchdog-device=</varname>) will be
|
|
|
|
|
programmed to automatically reboot the system if it is not contacted within the specified timeout interval. The
|
|
|
|
|
system manager will ensure to contact it at least once in half the specified timeout interval. This feature
|
|
|
|
|
requires a hardware watchdog device to be present, as it is commonly the case in embedded and server
|
|
|
|
|
systems. Not all hardware watchdogs allow configuration of all possible reboot timeout values, in which case
|
2019-07-22 18:39:25 +08:00
|
|
|
the closest available timeout is picked. <varname>RebootWatchdogSec=</varname> may be used to configure the
|
2018-03-22 05:00:21 +08:00
|
|
|
hardware watchdog when the system is asked to reboot. It works as a safety net to ensure that the reboot takes
|
2019-07-22 18:39:25 +08:00
|
|
|
place even if a clean reboot attempt times out. Note that the <varname>RebootWatchdogSec=</varname> timeout
|
2018-03-22 05:00:21 +08:00
|
|
|
applies only to the second phase of the reboot, i.e. after all regular services are already terminated, and
|
|
|
|
|
after the system and service manager process (PID 1) got replaced by the <filename>systemd-shutdown</filename>
|
|
|
|
|
binary, see system <citerefentry><refentrytitle>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
|
|
|
|
for details. During the first phase of the shutdown operation the system and service manager remains running
|
|
|
|
|
and hence <varname>RuntimeWatchdogSec=</varname> is still honoured. In order to define a timeout on this first
|
|
|
|
|
phase of system shutdown, configure <varname>JobTimeoutSec=</varname> and <varname>JobTimeoutAction=</varname>
|
2020-07-06 17:00:06 +08:00
|
|
|
in the [Unit] section of the <filename>shutdown.target</filename> unit. By default
|
2019-07-22 18:39:25 +08:00
|
|
|
<varname>RuntimeWatchdogSec=</varname> defaults to 0 (off), and <varname>RebootWatchdogSec=</varname> to
|
2019-07-19 18:54:15 +08:00
|
|
|
10min. <varname>KExecWatchdogSec=</varname> may be used to additionally enable the watchdog when kexec
|
|
|
|
|
is being executed rather than when rebooting. Note that if the kernel does not reset the watchdog on kexec (depending
|
|
|
|
|
on the specific hardware and/or driver), in this case the watchdog might not get disabled after kexec succeeds
|
|
|
|
|
and thus the system might get rebooted, unless <varname>RuntimeWatchdogSec=</varname> is also enabled at the same time.
|
|
|
|
|
For this reason it is recommended to enable <varname>KExecWatchdogSec=</varname> only if
|
|
|
|
|
<varname>RuntimeWatchdogSec=</varname> is also enabled.
|
|
|
|
|
These settings have no effect if a hardware watchdog is not available.</para></listitem>
|
2015-02-04 10:14:13 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2017-12-09 01:27:01 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>WatchdogDevice=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configure the hardware watchdog device that the
|
|
|
|
|
runtime and shutdown watchdog timers will open and use. Defaults
|
|
|
|
|
to <filename>/dev/watchdog</filename>. This setting has no
|
|
|
|
|
effect if a hardware watchdog is not available.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 10:14:13 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>CapabilityBoundingSet=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Controls which capabilities to include in the
|
|
|
|
|
capability bounding set for PID 1 and its children. See
|
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
|
|
|
|
for details. Takes a whitespace-separated list of capability
|
|
|
|
|
names as read by
|
2015-03-14 10:22:39 +08:00
|
|
|
<citerefentry project='mankier'><refentrytitle>cap_from_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
|
2015-02-04 10:14:13 +08:00
|
|
|
Capabilities listed will be included in the bounding set, all
|
|
|
|
|
others are removed. If the list of capabilities is prefixed
|
|
|
|
|
with ~, 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. The capability
|
|
|
|
|
bounding set may also be individually configured for units
|
|
|
|
|
using the <varname>CapabilityBoundingSet=</varname> directive
|
|
|
|
|
for units, but note that capabilities dropped for PID 1 cannot
|
|
|
|
|
be regained in individual units, they are lost for
|
|
|
|
|
good.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2018-03-22 06:41:19 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>NoNewPrivileges=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a boolean argument. If true, ensures that PID 1
|
|
|
|
|
and all its children can never gain new privileges through
|
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>execve</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
|
|
|
|
(e.g. via setuid or setgid bits, or filesystem capabilities).
|
|
|
|
|
Defaults to false. General purpose distributions commonly rely
|
|
|
|
|
on executables with setuid or setgid bits and will thus not
|
|
|
|
|
function properly with this option enabled. Individual units
|
|
|
|
|
cannot disable this option.
|
|
|
|
|
Also see <ulink url="https://www.kernel.org/doc/html/latest/userspace-api/no_new_privs.html">No New Privileges Flag</ulink>.
|
|
|
|
|
</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 10:14:13 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>SystemCallArchitectures=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a space-separated list of architecture
|
|
|
|
|
identifiers. Selects from which architectures system calls may
|
|
|
|
|
be invoked on this system. This may be used as an effective
|
|
|
|
|
way to disable invocation of non-native binaries system-wide,
|
|
|
|
|
for example to prohibit execution of 32-bit x86 binaries on
|
|
|
|
|
64-bit x86-64 systems. This option operates system-wide, and
|
|
|
|
|
acts similar to the
|
|
|
|
|
<varname>SystemCallArchitectures=</varname> setting of unit
|
|
|
|
|
files, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details. This setting defaults to the empty list, in which
|
|
|
|
|
case no filtering of system calls based on architecture is
|
|
|
|
|
applied. Known architecture identifiers are
|
|
|
|
|
<literal>x86</literal>, <literal>x86-64</literal>,
|
|
|
|
|
<literal>x32</literal>, <literal>arm</literal> and the special
|
|
|
|
|
identifier <literal>native</literal>. The latter implicitly
|
|
|
|
|
maps to the native architecture of the system (or more
|
|
|
|
|
specifically, the architecture the system manager was compiled
|
|
|
|
|
for). Set this setting to <literal>native</literal> to
|
|
|
|
|
prohibit execution of any non-native binaries. When a binary
|
|
|
|
|
executes a system call of an architecture that is not listed
|
|
|
|
|
in this setting, it will be immediately terminated with the
|
|
|
|
|
SIGSYS signal.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>TimerSlackNSec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Sets the timer slack in nanoseconds for PID 1,
|
|
|
|
|
which is inherited by all executed processes, unless
|
|
|
|
|
overridden individually, for example with the
|
|
|
|
|
<varname>TimerSlackNSec=</varname> setting in service units
|
|
|
|
|
(for details see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
|
|
|
|
|
The timer slack controls the accuracy of wake-ups triggered by
|
|
|
|
|
system timers. See
|
|
|
|
|
<citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
|
|
|
|
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.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2019-06-07 01:22:20 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>StatusUnitFormat=</varname></term>
|
|
|
|
|
|
2021-06-26 23:50:16 +08:00
|
|
|
<listitem><para>Takes <option>name</option>, <option>description</option> or
|
|
|
|
|
<option>combined</option> as the value. If <option>name</option>, the system manager will use unit
|
core: rework unit printing and implement 'combined' format
The code to print unit status formats had a long history, and became a
hard-to-manage mess of duplicate code parts. We would use sprintf() to
format a string, and then call sprintf() again… The code is reworked
to avoid repeated formattings and to streamline printing to the log
and the console.
The approach used in this patch is a bit more complex then in patches by Colin
Walter and Paweł Marciniak, because an allocation is only done if "combined"
format is used. In other cases we return the existing ->id or ->description
strings. The caller can also control whether a shorter or longer status string
should be used. This way the caller can use a shorter format where it makes
sense, for example in the cylon eye output, where we don't have enough
horizontal space.
Patch is based on Colin Walters' https://github.com/systemd/systemd/pull/15957,
and Paweł Marciniak's patch posted on fedora-devel.
Note: for some reason, the functions for printing of start and stop messages
were sepearated by some unrelated functions. They are moved to be consecutive,
but this makes the much more verbose than it would be otherwise. I found it
useful to view in gitk's "new" mode.
Co-authored-by: Colin Walters <walters@verbum.org>
Co-authored-by: Paweł Marciniak <sunwire+git@gmail.com>
Output from a Fedora Rawhide container boot (w/ some follow-up patches to
tweak Descriptions):
Welcome to Fedora 35 (Rawhide Prerelease)!
Queued start job for default target graphical.target.
[ OK ] Created slice system-getty.slice - Slice /system/getty.
[ OK ] Created slice system-modprobe.slice - Slice /system/modprobe.
[ OK ] Created slice system-sshd\x2dkeygen.slice - Slice /system/sshd-keygen.
[ OK ] Created slice user.slice - User and Session Slice.
[ OK ] Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch.
[ OK ] Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[ OK ] Reached target cryptsetup.target - Local Encrypted Volumes.
[ OK ] Reached target paths.target - Path Units.
[ OK ] Reached target remote-cryptsetup.target - Remote Encrypted Volumes.
[ OK ] Reached target remote-fs.target - Remote File Systems.
[ OK ] Reached target slices.target - Slice Units.
[ OK ] Reached target swap.target - Swaps.
[ OK ] Reached target veritysetup.target - Local Verity Integrity Protected Volumes.
[ OK ] Listening on systemd-coredump.socket - Process Core Dump Socket.
[ OK ] Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
[ OK ] Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
[ OK ] Listening on systemd-journald.socket - Journal Socket.
[ OK ] Listening on systemd-networkd.socket - Network Service Netlink Socket.
[ OK ] Listening on systemd-userdbd.socket - User Database Manager Socket.
Mounting dev-hugepages.mount - Huge Pages File System...
Starting systemd-journald.service - Journal Service...
Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
Starting systemd-sysctl.service - Apply Kernel Variables...
[ OK ] Mounted dev-hugepages.mount - Huge Pages File System.
[ OK ] Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.
Starting systemd-hwdb-update.service - Rebuild Hardware Database...
Starting systemd-sysusers.service - Create System Users...
[ OK ] Finished systemd-sysctl.service - Apply Kernel Variables.
[ OK ] Started systemd-journald.service - Journal Service.
Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
[ OK ] Finished systemd-sysusers.service - Create System Users.
Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev...
[ OK ] Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
[ OK ] Reached target local-fs-pre.target - Preparation for Local File Systems.
[ OK ] Reached target local-fs.target - Local File Systems.
[ OK ] Reached target machines.target - Containers.
Starting dracut-shutdown.service - Restore /run/initramfs on shutdown...
Starting ldconfig.service - Rebuild Dynamic Linker Cache...
[ OK ] Finished dracut-shutdown.service - Restore /run/initramfs on shutdown.
[ OK ] Finished ldconfig.service - Rebuild Dynamic Linker Cache.
[ OK ] Finished systemd-journal-flush.service - Flush Journal to Persistent Storage.
Starting systemd-tmpfiles-setup.service - Create Volatile Files and Directories...
[ OK ] Finished systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
Starting systemd-journal-catalog-update.service - Rebuild Journal Catalog...
Starting systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer...
Starting systemd-update-utmp.service - Update UTMP about System Boot/Shutdown...
Starting systemd-userdbd.service - User Database Manager...
[ OK ] Finished systemd-update-utmp.service - Update UTMP about System Boot/Shutdown.
[ OK ] Finished systemd-journal-catalog-update.service - Rebuild Journal Catalog.
[ OK ] Started systemd-userdbd.service - User Database Manager.
[ OK ] Started systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer.
[ OK ] Finished systemd-hwdb-update.service - Rebuild Hardware Database.
Starting systemd-networkd.service - Network Configuration...
Starting systemd-update-done.service - Update is Completed...
[ OK ] Finished systemd-update-done.service - Update is Completed.
[ OK ] Reached target sysinit.target - System Initialization.
[ OK ] Started dnf-makecache.timer - dnf makecache --timer.
[ OK ] Started logrotate.timer - Daily rotation of log files.
[ OK ] Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[ OK ] Reached target timers.target - Timer Units.
[ OK ] Listening on dbus.socket - D-Bus System Message Bus Socket.
[ OK ] Reached target sockets.target - Socket Units.
[ OK ] Reached target basic.target - Basic System.
[ OK ] Reached target sshd-keygen.target.
Starting sysstat.service - Resets System Activity Logs...
Starting systemd-homed.service - Home Area Manager...
Starting systemd-logind.service - User Login Management...
Starting dbus-broker.service - D-Bus System Message Bus...
[FAILED] Failed to start sysstat.service - Resets System Activity Logs.
See 'systemctl status sysstat.service' for details.
[ OK ] Started dbus-broker.service - D-Bus System Message Bus.
[ OK ] Started systemd-homed.service - Home Area Manager.
[ OK ] Finished systemd-homed-activate.service - Home Area Activation.
[ OK ] Started systemd-logind.service - User Login Management.
[ OK ] Started systemd-networkd.service - Network Configuration.
Starting systemd-networkd-wait-online.service - Wait for Network to be Configured...
Starting systemd-resolved.service - Network Name Resolution...
[ OK ] Started systemd-resolved.service - Network Name Resolution.
[ OK ] Reached target network.target - Network.
[ OK ] Reached target nss-lookup.target - Host and Network Name Lookups.
Starting sshd.service - OpenSSH server daemon...
Starting systemd-user-sessions.service - Permit User Sessions...
[ OK ] Finished systemd-user-sessions.service - Permit User Sessions.
[ OK ] Started console-getty.service - Console Getty.
[ OK ] Reached target getty.target - Login Prompts.
[ OK ] Started sshd.service - OpenSSH server daemon.
[ OK ] Reached target multi-user.target - Multi-User System.
[ OK ] Reached target graphical.target - Graphical Interface.
Starting systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel Changes...
[ OK ] Finished systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel Changes.
Fedora 35 (Rawhide Prerelease)
Kernel 5.12.12-300.fc34.x86_64 on an x86_64 (console)
rawhide login: [ OK ] Stopped session-24.scope - Session 24 of User zbyszek.
[ OK ] Removed slice system-getty.slice - Slice /system/getty.
[ OK ] Removed slice system-modprobe.slice - Slice /system/modprobe.
[ OK ] Removed slice system-sshd\x2dkeygen.slice - Slice /system/sshd-keygen.
[ OK ] Stopped target graphical.target - Graphical Interface.
[ OK ] Stopped target multi-user.target - Multi-User System.
[ OK ] Stopped target getty.target - Login Prompts.
[ OK ] Stopped target machines.target - Containers.
[ OK ] Stopped target nss-lookup.target - Host and Network Name Lookups.
[ OK ] Stopped target remote-cryptsetup.target - Remote Encrypted Volumes.
[ OK ] Stopped target timers.target - Timer Units.
[ OK ] Stopped dnf-makecache.timer - dnf makecache --timer.
[ OK ] Stopped logrotate.timer - Daily rotation of log files.
[ OK ] Stopped systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[ OK ] Closed systemd-coredump.socket - Process Core Dump Socket.
Stopping console-getty.service - Console Getty...
Stopping dracut-shutdown.service - Restore /run/initramfs on shutdown...
Stopping sshd.service - OpenSSH server daemon...
Stopping systemd-logind.service - User Login Management...
Stopping systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer...
Stopping user@1000.service - User Manager for UID 1000...
[ OK ] Stopped systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer.
[ OK ] Stopped systemd-networkd-wait-online.service - Wait for Network to be Configured.
[ OK ] Stopped sshd.service - OpenSSH server daemon.
[ OK ] Stopped console-getty.service - Console Getty.
[ OK ] Stopped dracut-shutdown.service - Restore /run/initramfs on shutdown.
[ OK ] Stopped target sshd-keygen.target.
[ OK ] Stopped systemd-logind.service - User Login Management.
[ OK ] Stopped user@1000.service - User Manager for UID 1000.
Stopping user-runtime-dir@1000.service - User Runtime Directory /run/user/1000...
[ OK ] Unmounted run-user-1000.mount - /run/user/1000.
[ OK ] Stopped user-runtime-dir@1000.service - User Runtime Directory /run/user/1000.
[ OK ] Removed slice user-1000.slice - User Slice of UID 1000.
Stopping systemd-user-sessions.service - Permit User Sessions...
[ OK ] Stopped systemd-user-sessions.service - Permit User Sessions.
[ OK ] Stopped target network.target - Network.
[ OK ] Stopped target remote-fs.target - Remote File Systems.
Stopping systemd-homed-activate.service - Home Area Activation...
Stopping systemd-resolved.service - Network Name Resolution...
[ OK ] Stopped systemd-resolved.service - Network Name Resolution.
Stopping systemd-networkd.service - Network Configuration...
[ OK ] Stopped systemd-homed-activate.service - Home Area Activation.
Stopping systemd-homed.service - Home Area Manager...
[ OK ] Stopped systemd-homed.service - Home Area Manager.
[ OK ] Stopped target basic.target - Basic System.
[ OK ] Stopped target paths.target - Path Units.
[ OK ] Stopped target slices.target - Slice Units.
[ OK ] Removed slice user.slice - User and Session Slice.
[ OK ] Stopped target sockets.target - Socket Units.
Stopping dbus-broker.service - D-Bus System Message Bus...
[ OK ] Stopped dbus-broker.service - D-Bus System Message Bus.
[ OK ] Closed dbus.socket - D-Bus System Message Bus Socket.
[ OK ] Stopped target sysinit.target - System Initialization.
[ OK ] Stopped target cryptsetup.target - Local Encrypted Volumes.
[ OK ] Stopped systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch.
[ OK ] Stopped systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[ OK ] Stopped target veritysetup.target - Local Verity Integrity Protected Volumes.
[ OK ] Stopped systemd-update-done.service - Update is Completed.
[ OK ] Stopped ldconfig.service - Rebuild Dynamic Linker Cache.
[ OK ] Stopped systemd-hwdb-update.service - Rebuild Hardware Database.
[ OK ] Stopped systemd-journal-catalog-update.service - Rebuild Journal Catalog.
Stopping systemd-update-utmp.service - Update UTMP about System Boot/Shutdown...
[ OK ] Stopped systemd-networkd.service - Network Configuration.
[ OK ] Closed systemd-networkd.socket - Network Service Netlink Socket.
[ OK ] Stopped systemd-sysctl.service - Apply Kernel Variables.
[ OK ] Stopped systemd-update-utmp.service - Update UTMP about System Boot/Shutdown.
[ OK ] Stopped systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
[ OK ] Stopped target local-fs.target - Local File Systems.
Unmounting home.mount - /home...
Unmounting run-credentials-systemd\x2dsysusers.se…e.mount - /run/credentials/systemd-sysusers.service...
Unmounting tmp.mount - Temporary Directory /tmp...
[ OK ] Unmounted home.mount - /home.
[ OK ] Unmounted tmp.mount - Temporary Directory /tmp.
[ OK ] Unmounted run-credentials-systemd\x2dsysusers.service.mount - /run/credentials/systemd-sysusers.service.
[ OK ] Stopped target local-fs-pre.target - Preparation for Local File Systems.
[ OK ] Stopped target swap.target - Swaps.
[ OK ] Reached target umount.target - Unmount All Filesystems.
[ OK ] Stopped systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
[ OK ] Stopped systemd-sysusers.service - Create System Users.
[ OK ] Stopped systemd-remount-fs.service - Remount Root and Kernel File Systems.
[ OK ] Reached target shutdown.target - System Shutdown.
[ OK ] Reached target final.target - Late Boot Services.
[ OK ] Finished systemd-poweroff.service - System Power Off.
[ OK ] Reached target poweroff.target - System Power Off.
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
All filesystems, swaps, loop devices, MD devices and DM devices detached.
Powering off.
2021-06-29 02:07:15 +08:00
|
|
|
names in status messages (e.g. <literal>systemd-journald.service</literal>), instead of the longer
|
|
|
|
|
and more informative descriptions set with <varname>Description=</varname> (e.g. <literal>Journal
|
|
|
|
|
Logging Service</literal>). If <option>combined</option>, the system manager will use both unit names
|
|
|
|
|
and descriptions in status messages (e.g. <literal>systemdmd-jouranld.service - Journal Logging
|
|
|
|
|
Service</literal>).</para>
|
|
|
|
|
|
|
|
|
|
<para>See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
|
|
|
|
|
details about unit names and <varname>Description=</varname>.</para></listitem>
|
2019-06-07 01:22:20 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 10:14:13 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultTimerAccuracySec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Sets the default accuracy of timer units. This
|
|
|
|
|
controls the global default for the
|
|
|
|
|
<varname>AccuracySec=</varname> setting of timer units, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details. <varname>AccuracySec=</varname> set in individual
|
|
|
|
|
units override the global default for the specific unit.
|
|
|
|
|
Defaults to 1min. Note that the accuracy of timer units is
|
|
|
|
|
also affected by the configured timer slack for PID 1, see
|
|
|
|
|
<varname>TimerSlackNSec=</varname> above.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultTimeoutStartSec=</varname></term>
|
|
|
|
|
<term><varname>DefaultTimeoutStopSec=</varname></term>
|
2017-11-29 14:43:44 +08:00
|
|
|
<term><varname>DefaultTimeoutAbortSec=</varname></term>
|
2015-02-04 10:14:13 +08:00
|
|
|
<term><varname>DefaultRestartSec=</varname></term>
|
|
|
|
|
|
2017-11-29 14:43:44 +08:00
|
|
|
<listitem><para>Configures the default timeouts for starting,
|
|
|
|
|
stopping and aborting of units, as well as the default time to sleep
|
2015-02-04 10:14:13 +08:00
|
|
|
between automatic restarts of units, as configured per-unit in
|
|
|
|
|
<varname>TimeoutStartSec=</varname>,
|
2017-11-29 14:43:44 +08:00
|
|
|
<varname>TimeoutStopSec=</varname>,
|
|
|
|
|
<varname>TimeoutAbortSec=</varname> and
|
2015-02-04 10:14:13 +08:00
|
|
|
<varname>RestartSec=</varname> (for services, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
2019-01-15 20:52:34 +08:00
|
|
|
for details on the per-unit settings). Disabled by default, when
|
|
|
|
|
service with <varname>Type=oneshot</varname> is used.
|
|
|
|
|
For non-service units,
|
2015-02-04 10:14:13 +08:00
|
|
|
<varname>DefaultTimeoutStartSec=</varname> sets the default
|
2015-04-07 02:34:11 +08:00
|
|
|
<varname>TimeoutSec=</varname>
|
|
|
|
|
value. <varname>DefaultTimeoutStartSec=</varname> and
|
|
|
|
|
<varname>DefaultTimeoutStopSec=</varname> default to
|
2017-11-29 14:43:44 +08:00
|
|
|
90s. <varname>DefaultTimeoutAbortSec=</varname> is not set by default
|
|
|
|
|
so that all units fall back to <varname>TimeoutStopSec=</varname>.
|
|
|
|
|
<varname>DefaultRestartSec=</varname> defaults to
|
2015-04-07 02:34:11 +08:00
|
|
|
100ms.</para></listitem>
|
2015-02-04 10:14:13 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
2016-04-27 02:46:20 +08:00
|
|
|
<term><varname>DefaultStartLimitIntervalSec=</varname></term>
|
2015-02-04 10:14:13 +08:00
|
|
|
<term><varname>DefaultStartLimitBurst=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configure the default unit start rate
|
|
|
|
|
limiting, as configured per-service by
|
2016-04-27 02:46:20 +08:00
|
|
|
<varname>StartLimitIntervalSec=</varname> and
|
2015-02-04 10:14:13 +08:00
|
|
|
<varname>StartLimitBurst=</varname>. See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
2015-04-07 02:34:11 +08:00
|
|
|
for details on the per-service settings.
|
2016-04-27 02:46:20 +08:00
|
|
|
<varname>DefaultStartLimitIntervalSec=</varname> defaults to
|
2015-04-07 02:34:11 +08:00
|
|
|
10s. <varname>DefaultStartLimitBurst=</varname> defaults to
|
|
|
|
|
5.</para></listitem>
|
2015-02-04 10:14:13 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultEnvironment=</varname></term>
|
|
|
|
|
|
2021-02-19 07:06:26 +08:00
|
|
|
<listitem><para>Configures environment variables passed to all executed processes. Takes a
|
|
|
|
|
space-separated list of variable assignments. See <citerefentry
|
|
|
|
|
project='man-pages'><refentrytitle>environ</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
|
|
|
|
|
details about environment variables.</para>
|
2015-02-04 10:14:13 +08:00
|
|
|
|
2021-05-26 23:17:11 +08:00
|
|
|
<para>Simple <literal>%</literal>-specifier expansion is supported, see below for a list of supported
|
|
|
|
|
specifiers.</para>
|
|
|
|
|
|
2015-02-04 10:14:13 +08:00
|
|
|
<para>Example:
|
|
|
|
|
|
|
|
|
|
<programlisting>DefaultEnvironment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"</programlisting>
|
|
|
|
|
|
|
|
|
|
Sets three variables
|
|
|
|
|
<literal>VAR1</literal>,
|
|
|
|
|
<literal>VAR2</literal>,
|
|
|
|
|
<literal>VAR3</literal>.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2021-02-19 07:06:26 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>ManagerEnvironment=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes the same arguments as <varname>DefaultEnvironment=</varname>, see above. Sets
|
2021-05-18 16:23:36 +08:00
|
|
|
environment variables just for the manager process itself. In contrast to user managers, these variables
|
|
|
|
|
are not inherited by processes spawned by the system manager, use <varname>DefaultEnvironment=</varname>
|
|
|
|
|
for that. Note that these variables are merged into the existing environment block. In particular, in
|
|
|
|
|
case of the system manager, this includes variables set by the kernel based on the kernel command line.</para>
|
2021-02-19 07:06:26 +08:00
|
|
|
|
|
|
|
|
<para>Setting environment variables for the manager process may be useful to modify its behaviour.
|
|
|
|
|
See <ulink url="https://systemd.io/ENVIRONMENT">ENVIRONMENT</ulink> for a descriptions of some
|
2021-05-26 23:17:11 +08:00
|
|
|
variables understood by <command>systemd</command>.</para>
|
|
|
|
|
|
|
|
|
|
<para>Simple <literal>%</literal>-specifier expansion is supported, see below for a list of supported
|
|
|
|
|
specifiers.</para>
|
|
|
|
|
</listitem>
|
2021-02-19 07:06:26 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 10:14:13 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultCPUAccounting=</varname></term>
|
|
|
|
|
<term><varname>DefaultBlockIOAccounting=</varname></term>
|
|
|
|
|
<term><varname>DefaultMemoryAccounting=</varname></term>
|
2015-09-10 18:32:16 +08:00
|
|
|
<term><varname>DefaultTasksAccounting=</varname></term>
|
2018-06-26 03:07:44 +08:00
|
|
|
<term><varname>DefaultIOAccounting=</varname></term>
|
2016-11-12 20:38:38 +08:00
|
|
|
<term><varname>DefaultIPAccounting=</varname></term>
|
2015-02-04 10:14:13 +08:00
|
|
|
|
2016-11-12 20:38:38 +08:00
|
|
|
<listitem><para>Configure the default resource accounting settings, as configured per-unit by
|
|
|
|
|
<varname>CPUAccounting=</varname>, <varname>BlockIOAccounting=</varname>, <varname>MemoryAccounting=</varname>,
|
2018-06-26 03:07:44 +08:00
|
|
|
<varname>TasksAccounting=</varname>, <varname>IOAccounting=</varname> and <varname>IPAccounting=</varname>. See
|
2015-02-04 10:14:13 +08:00
|
|
|
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
2018-10-25 04:08:07 +08:00
|
|
|
for details on the per-unit settings. <varname>DefaultTasksAccounting=</varname> defaults to yes,
|
2018-10-25 21:03:58 +08:00
|
|
|
<varname>DefaultMemoryAccounting=</varname> to &MEMORY_ACCOUNTING_DEFAULT;. <varname>DefaultCPUAccounting=</varname>
|
|
|
|
|
defaults to yes if enabling CPU accounting doesn't require the CPU controller to be enabled (Linux 4.15+ using the
|
|
|
|
|
unified hierarchy for resource control), otherwise it defaults to no. The other three settings default to no.</para></listitem>
|
2015-02-04 10:14:13 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-11-14 00:13:55 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultTasksMax=</varname></term>
|
|
|
|
|
|
2016-07-19 23:29:00 +08:00
|
|
|
<listitem><para>Configure the default value for the per-unit <varname>TasksMax=</varname> setting. See
|
2015-11-14 00:13:55 +08:00
|
|
|
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
2016-07-19 23:29:00 +08:00
|
|
|
for details. This setting applies to all unit types that support resource control settings, with the exception
|
2021-01-30 11:14:35 +08:00
|
|
|
of slice units. Defaults to 15% of the minimum of <varname>kernel.pid_max=</varname>, <varname>kernel.threads-max=</varname>
|
|
|
|
|
and root cgroup <varname>pids.max</varname>.
|
2020-11-18 22:54:01 +08:00
|
|
|
Kernel has a default value for <varname>kernel.pid_max=</varname> and an algorithm of counting in case of more than 32 cores.
|
|
|
|
|
For example with the default <varname>kernel.pid_max=</varname>, <varname>DefaultTasksMax=</varname> defaults to 4915,
|
|
|
|
|
but might be greater in other systems or smaller in OS containers.</para></listitem>
|
2015-11-14 00:13:55 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 10:14:13 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultLimitCPU=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitFSIZE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitDATA=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitSTACK=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitCORE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitRSS=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitNOFILE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitAS=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitNPROC=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitMEMLOCK=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitLOCKS=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitSIGPENDING=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitMSGQUEUE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitNICE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitRTPRIO=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitRTTIME=</varname></term>
|
|
|
|
|
|
2020-01-17 02:22:30 +08:00
|
|
|
<listitem><para>These settings control various default resource limits for processes executed by
|
|
|
|
|
units. See
|
|
|
|
|
<citerefentry><refentrytitle>setrlimit</refentrytitle><manvolnum>2</manvolnum></citerefentry> for
|
|
|
|
|
details. These settings may be overridden in individual units using the corresponding
|
2020-07-06 16:49:59 +08:00
|
|
|
<varname>LimitXXX=</varname> directives and they accept the same parameter syntax,
|
|
|
|
|
see <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details. Note that these resource limits are only defaults
|
2021-05-19 15:33:59 +08:00
|
|
|
for units, they are not applied to the service manager process (i.e. PID 1) itself.</para>
|
|
|
|
|
|
|
|
|
|
<para>Most of these settings are unset, which means the resource limits are inherited from the kernel or, if
|
|
|
|
|
invoked in a container, from the container manager. However, the following have defaults:</para>
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem><para><varname>DefaultLimitNOFILE=</varname> defaults to <literal>1024:&HIGH_RLIMIT_NOFILE;</literal>.
|
|
|
|
|
</para></listitem>
|
|
|
|
|
|
|
|
|
|
<listitem><para><varname>DefaultLimitCORE=</varname> does not have a default but it is worth mentioning that
|
|
|
|
|
<varname>RLIMIT_CORE</varname> is set to <literal>infinity</literal> by PID 1 which is inherited by its
|
|
|
|
|
children.</para></listitem>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Note that the service manager internally increases <varname>RLIMIT_MEMLOCK</varname> for
|
|
|
|
|
itself, however the limit is reverted to the original value for child processes forked off.</para></listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
|
|
|
|
|
</listitem>
|
2015-02-04 10:14:13 +08:00
|
|
|
</varlistentry>
|
2019-03-20 02:54:08 +08:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultOOMPolicy=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configure the default policy for reacting to processes being killed by the Linux
|
|
|
|
|
Out-Of-Memory (OOM) killer. This may be used to pick a global default for the per-unit
|
|
|
|
|
<varname>OOMPolicy=</varname> setting. See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details. Note that this default is not used for services that have <varname>Delegate=</varname>
|
|
|
|
|
turned on.</para></listitem>
|
|
|
|
|
</varlistentry>
|
2015-02-04 10:14:13 +08:00
|
|
|
</variablelist>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
2021-05-26 23:17:11 +08:00
|
|
|
<refsect1>
|
|
|
|
|
<title>Specifiers</title>
|
|
|
|
|
|
|
|
|
|
<para>Specifiers may be used in the <varname>DefaultEnvironment=</varname> and
|
|
|
|
|
<varname>ManagerEnvironment=</varname> settings. The following expansions are understood:</para>
|
|
|
|
|
<table class='specifiers'>
|
|
|
|
|
<title>Specifiers available</title>
|
|
|
|
|
<tgroup cols='3' align='left' colsep='1' rowsep='1'>
|
|
|
|
|
<colspec colname="spec" />
|
|
|
|
|
<colspec colname="mean" />
|
|
|
|
|
<colspec colname="detail" />
|
|
|
|
|
<thead>
|
|
|
|
|
<row>
|
|
|
|
|
<entry>Specifier</entry>
|
|
|
|
|
<entry>Meaning</entry>
|
|
|
|
|
<entry>Details</entry>
|
|
|
|
|
</row>
|
|
|
|
|
</thead>
|
|
|
|
|
<tbody>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="a"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="A"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="b"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="B"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="H"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="l"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="m"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="M"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="o"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="v"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="w"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="W"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="T"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="V"/>
|
|
|
|
|
<xi:include href="standard-specifiers.xml" xpointer="percent"/>
|
|
|
|
|
</tbody>
|
|
|
|
|
</tgroup>
|
|
|
|
|
</table>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
2015-02-04 10:14:13 +08:00
|
|
|
<refsect1>
|
|
|
|
|
<title>See Also</title>
|
|
|
|
|
<para>
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>environ</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
|
|
|
|
</para>
|
|
|
|
|
</refsect1>
|
2010-07-07 07:38:56 +08:00
|
|
|
|
|
|
|
|
</refentry>
|
