shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

man: update version information

Browse Source 
As I noticed a lot of missing information when trying to implement checking
for missing info. I reimplemented the version information script to be more
robust, and here is the result.

Follow up to ec07c3c80b
This commit is contained in:
Abderrahim Kitouni 2023-09-18 16:03:38 +01:00 committed by Luca Boccassi
parent 6b66407080
commit aefdc1124f
69 changed files with 1577 additions and 447 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
man/bootctl.xml
View File

@ -52,6 +52,8 @@
specified, this is the implied default.</para>
<para>See the example below for details of the output.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@ -94,6 +96,8 @@
JSON output may be requested with <option>--json=</option>.</para>
<para>See the example below for details of the output.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@ -159,7 +163,9 @@
<command>systemctl reboot --boot-loader-menu=<replaceable>timeout</replaceable></command>
to reboot into the boot loader menu once. See
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
for details.</para></listitem>
for details.</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
<varlistentry>
@ -174,7 +180,9 @@
<para>If this is set to <option>menu-hidden</option> or <option>0</option> no menu is shown and
the default entry will be booted immediately, while setting this to <option>menu-force</option>
disables the timeout while always showing the menu. When an empty string ("") is specified the
bootloader will revert to its default menu timeout.</para></listitem>
bootloader will revert to its default menu timeout.</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@ -192,7 +200,9 @@
<listitem><para>Installs <command>systemd-boot</command> into the EFI system partition. A copy of
<command>systemd-boot</command> will be stored as the EFI default/fallback loader at
<filename><replaceable>ESP</replaceable>/EFI/BOOT/BOOT*.EFI</filename>. The boot loader is then added
to the top of the firmware's boot loader list.</para></listitem>
to the top of the firmware's boot loader list.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -202,14 +212,18 @@
<citerefentry><refentrytitle>systemd-boot</refentrytitle><manvolnum>7</manvolnum></citerefentry>, if the
available version is newer than the version installed in the EFI system partition. This also includes the EFI
default/fallback loader at <filename><replaceable>ESP</replaceable>/EFI/BOOT/BOOT*.EFI</filename>. The boot
loader is then added to end of the firmware's boot loader list if missing.</para></listitem>
loader is then added to end of the firmware's boot loader list if missing.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><option>remove</option></term>
<listitem><para>Removes all installed versions of <command>systemd-boot</command> from the EFI system partition
and the firmware's boot loader list.</para></listitem>
and the firmware's boot loader list.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -218,7 +232,9 @@
<listitem><para>Checks whether <command>systemd-boot</command> is installed in the ESP. Note that a
single ESP might host multiple boot loaders; this hence checks whether
<command>systemd-boot</command> is one (of possibly many) installed boot loaders — and neither
whether it is the default nor whether it is registered in any EFI variables.</para></listitem>
whether it is the default nor whether it is registered in any EFI variables.</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
<varlistentry>
@ -235,7 +251,9 @@
<citerefentry><refentrytitle>systemd-boot-random-seed.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<para>See <ulink url="https://systemd.io/RANDOM_SEEDS">Random Seeds</ulink> for further
information.</para></listitem>
information.</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
</variablelist>
@ -316,7 +334,9 @@
<term><option>-p</option></term>
<term><option>--print-esp-path</option></term>
<listitem><para>This option modifies the behaviour of <command>status</command>. Only prints the path
to the EFI System Partition (ESP) to standard output and exits.</para></listitem>
to the EFI System Partition (ESP) to standard output and exits.</para>
<xi:include href="version-info.xml" xpointer="v236"/></listitem>
</varlistentry>
<varlistentry>
@ -335,7 +355,9 @@
<para>Note that this option (similarly to the <option>--print-boot-path</option> option mentioned
above), is available independently from the boot loader used, i.e. also without
<command>systemd-boot</command> being installed.</para></listitem>
<command>systemd-boot</command> being installed.</para>
<xi:include href="version-info.xml" xpointer="v242"/></listitem>
</varlistentry>
<varlistentry>

8
man/busctl.xml
View File

@ -64,7 +64,7 @@
the owner of the bus (if no parameter is
specified).</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -77,7 +77,7 @@
<keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>
to terminate the dump.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -116,7 +116,7 @@
output is limited to members of the specified
interface.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@ -285,6 +285,8 @@
if this option is specified, errors returned will still be
printed and the tool will indicate success or failure with
the process exit code.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>

18
man/coredumpctl.xml
View File

@ -121,7 +121,9 @@
<citerefentry><refentrytitle>systemd-coredump</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
Thus it may very well happen that a particular core dump is still listed
in the journal while its corresponding core dump file has already been
removed.</para></listitem>
removed.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -129,7 +131,9 @@
<listitem><para>Show detailed information about the last core dump
or core dumps matching specified characteristics
captured in the journal.</para></listitem>
captured in the journal.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -138,7 +142,9 @@
<listitem><para>Extract the last core dump matching specified
characteristics. The core dump will be written on standard
output, unless an output file is specified with
<option>--output=</option>. </para></listitem>
<option>--output=</option>. </para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -226,7 +232,7 @@
field takes in matching core dump entries of the
journal.</para>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -234,7 +240,9 @@
<term><option>--output=</option><replaceable>FILE</replaceable></term>
<listitem><para>Write the core to <option>FILE</option>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>

132
man/crypttab.xml
View File

@ -148,6 +148,8 @@
for possible values and the default value of this option. A cipher with unpredictable IV values, such
as <literal>aes-cbc-essiv:sha256</literal>, is recommended. Embedded commas in the cipher
specification need to be escaped by preceding them with a backslash, see example below.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -156,7 +158,9 @@
<listitem><para>Allow discard requests to be passed through the encrypted block
device. This improves performance on SSD storage but has security implications.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v207"/></listitem>
</varlistentry>
<varlistentry>
@ -166,7 +170,9 @@
hashing. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this
option.</para></listitem>
option.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -181,7 +187,9 @@
<para>Optionally, the path may be followed by <literal>:</literal> and an
<filename>/etc/fstab</filename> device specification (e.g. starting with <literal>UUID=</literal> or
similar); in which case, the path is relative to the device file system root. The device gets mounted
automatically for LUKS device activation duration only.</para></listitem>
automatically for LUKS device activation duration only.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -191,7 +199,9 @@
start of the key file. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this
option.</para></listitem>
option.</para>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
<varlistentry>
@ -202,7 +212,9 @@
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this option. This
option is ignored in plain encryption mode, as the key file
size is then given by the key size.</para></listitem>
size is then given by the key size.</para>
<xi:include href="version-info.xml" xpointer="v188"/></listitem>
</varlistentry>
<varlistentry>
@ -211,7 +223,9 @@
<listitem><para>If enabled, the specified key file is erased after the volume is activated or when
activation fails. This is in particular useful when the key file is only acquired transiently before
activation (e.g. via a file in <filename>/run/</filename>, generated by a service running before
activation), and shall be removed after use. Defaults to off.</para></listitem>
activation), and shall be removed after use. Defaults to off.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@ -224,7 +238,9 @@
<option>luks</option>. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values. The default is to try all key slots in
sequential order.</para></listitem>
sequential order.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -235,7 +251,9 @@
and falls back to a password if it could not be accessed. See
<citerefentry><refentrytitle>systemd-cryptsetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for key files on external devices.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
<varlistentry>
@ -245,14 +263,18 @@
following options are ignored since they are provided by the
LUKS header on the device: <option>cipher=</option>,
<option>hash=</option>,
<option>size=</option>.</para></listitem>
<option>size=</option>.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
<term><option>bitlk</option></term>
<listitem><para>Decrypt BitLocker drive. Encryption parameters
are deduced by cryptsetup from BitLocker header.</para></listitem>
are deduced by cryptsetup from BitLocker header.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@ -274,6 +296,8 @@
will be pulled in by <filename>local-fs.target</filename>, while the
service to configure the network is usually only started <emphasis>after</emphasis>
the local file system has been mounted.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@ -284,7 +308,9 @@
This means that it will not be automatically unlocked on boot, unless something else pulls
it in. In particular, if the device is used for a mount point, it'll be unlocked
automatically during boot, unless the mount point itself is also disabled with
<option>noauto</option>.</para></listitem>
<option>noauto</option>.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -296,27 +322,35 @@
unsuccessful. Note that other units that depend on the unlocked device may still fail. In
particular, if the device is used for a mount point, the mount point itself also needs to
have the <option>nofail</option> option, or the boot will fail if the device is not unlocked
successfully.</para></listitem>
successfully.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
<term><option>offset=</option></term>
<listitem><para>Start offset in the backend device, in 512-byte sectors. This
option is only relevant for plain devices.</para></listitem>
option is only relevant for plain devices.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
<term><option>plain</option></term>
<listitem><para>Force plain encryption mode.</para></listitem>
<listitem><para>Force plain encryption mode.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
<term><option>read-only</option></term><term><option>readonly</option></term>
<listitem><para>Set up the encrypted block device in read-only
mode.</para></listitem>
mode.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -326,6 +360,8 @@
an unbound workqueue so that encryption work is automatically balanced between available CPUs.</para>
<para>This requires kernel 4.0 or newer.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@ -338,6 +374,8 @@
benefits the CFQ scheduler to have writes submitted using the same context.</para>
<para>This requires kernel 4.0 or newer.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@ -378,6 +416,8 @@
with its number for IV generation being <replaceable>n</replaceable>.</para>
<para>This option is only relevant for plain devices.</para>
<xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
@ -387,7 +427,9 @@
<listitem><para>Specifies the key size in bits. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this
option.</para></listitem>
option.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -396,7 +438,9 @@
<listitem><para>Specifies the sector size in bytes. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this
option.</para></listitem>
option.</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
<varlistentry>
@ -411,7 +455,9 @@
<para>WARNING: Using the <option>swap</option> option will
destroy the contents of the named partition during every boot,
so make sure the underlying block device is specified
correctly.</para></listitem>
correctly.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -438,7 +484,9 @@
to all key files. When using an empty passphrase in
combination with one or more key files, use
<literal>/dev/null</literal> as the password file in the third
field.</para></listitem>
field.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -452,7 +500,9 @@
no protection for the hidden volume if the outer volume is
mounted instead. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for more information on this limitation.</para></listitem>
for more information on this limitation.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -465,14 +515,18 @@
<para>See the entry for <option>tcrypt</option> on the
behavior of the passphrase and key files when using TrueCrypt
encryption mode.</para></listitem>
encryption mode.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
<term><option>tcrypt-system</option></term>
<listitem><para>Use TrueCrypt in system encryption mode. This
option implies <option>tcrypt</option>.</para></listitem>
option implies <option>tcrypt</option>.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -483,7 +537,9 @@
derivation algorithms that cannot be detected without this flag.
Enabling this option could substantially slow down unlocking, because
VeraCrypt's key derivation takes much longer than TrueCrypt's. This
option implies <option>tcrypt</option>.</para></listitem>
option implies <option>tcrypt</option>.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -513,7 +569,9 @@
<listitem><para>Specifies the timeout for querying for a
password. If no unit is specified, seconds is used. Supported
units are s, ms, us, min, h, d. A timeout of 0 waits
indefinitely (which is the default).</para></listitem>
indefinitely (which is the default).</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -527,7 +585,9 @@
option implies <option>plain</option>.</para>
<para>WARNING: Using the <option>tmp</option> option will destroy the contents of the named partition
during every boot, so make sure the underlying block device is specified correctly.</para></listitem>
during every boot, so make sure the underlying block device is specified correctly.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -535,7 +595,9 @@
<listitem><para>Specifies the maximum number of times the user
is queried for a password. The default is 3. If set to 0, the
user is queried for a password indefinitely.</para></listitem>
user is queried for a password indefinitely.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -551,7 +613,9 @@
<term><option>verify</option></term>
<listitem><para>If the encryption password is read from console, it has to be entered twice to
prevent typos.</para></listitem>
prevent typos.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -604,7 +668,9 @@
implement the newer and simpler FIDO2 standard. Consider using <option>fido2-device=</option>
(described below) to enroll it via FIDO2 instead. Note that a security token enrolled via PKCS#11
cannot be used to unlock the volume via FIDO2, unless also enrolled via FIDO2, and vice
versa.</para></listitem>
versa.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@ -788,7 +854,9 @@
<listitem><para>Takes a boolean argument. If enabled, right before asking the user for a password it
is first attempted to unlock the volume with an empty password. This is useful for systems that are
initialized with an encrypted volume with only an empty password set, which shall be replaced with a
suitable password during first boot, but after activation.</para></listitem>
suitable password during first boot, but after activation.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@ -797,7 +865,9 @@
<listitem><para>Specifies how long systemd should wait for a block device to show up before
giving up on the entry. The argument is a time in seconds or explicitly specified units of
<literal>s</literal>, <literal>min</literal>, <literal>h</literal>, <literal>ms</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
<varlistentry>
@ -816,6 +886,8 @@
<para>All other encrypted block devices that contain file systems mounted in the initrd should use
this option.</para>
<xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>

78
man/file-hierarchy.xml
View File

@ -68,7 +68,7 @@
systems that run on physical or emulated hardware that
requires boot loaders.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -92,7 +92,7 @@
back to defaults if configuration is
missing.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -111,7 +111,7 @@
environment variable, or via the home directory field of the
user database.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -122,7 +122,7 @@
may log in even without <filename>/home/</filename> being
available and mounted.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -134,7 +134,7 @@
available or writable only very late during
boot.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -158,7 +158,7 @@
and similar calls. For more details, see <ulink url="https://systemd.io/TEMPORARY_DIRECTORIES">Using
/tmp/ and /var/tmp/ Safely</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -175,7 +175,7 @@
socket files, and similar. This directory is flushed on boot, and generally writable for privileged
programs only. Always writable.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -185,7 +185,7 @@
when <filename>/var/log/</filename> might not be accessible
yet.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -200,7 +200,7 @@
url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
Base Directory Specification</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@ -218,7 +218,7 @@
by the administrator, except when installing or removing
vendor-supplied packages.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -230,7 +230,7 @@
binaries); these should be placed in a subdirectory of
<filename>/usr/lib/</filename> instead.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -238,7 +238,7 @@
<listitem><para>C and C++ API header files of system
libraries.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -252,7 +252,7 @@
directory, use <varname>$libdir</varname> (see below),
instead.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -271,7 +271,7 @@
system, invoke:
<programlisting># systemd-path system-library-arch</programlisting></para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
@ -283,7 +283,7 @@
of files stored below this directory is subject to
specifications that ensure interoperability.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -291,7 +291,7 @@
<listitem><para>Documentation for the operating system or
system packages.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -304,7 +304,7 @@
defaults and to populate the local configuration with
defaults.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -315,7 +315,7 @@
versions of files in the variable, persistent data directory
<filename>/var/</filename>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>
@ -335,7 +335,7 @@
late during boot. Components that are required to operate during early boot hence shall not
unconditionally rely on this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -346,7 +346,7 @@
programs, except for increased runtimes necessary to rebuild
these caches.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -354,7 +354,7 @@
<listitem><para>Persistent system data. System components may
place private data in this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -367,7 +367,7 @@
<citerefentry><refentrytitle>sd_journal_print</refentrytitle><manvolnum>3</manvolnum></citerefentry>
calls.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -375,7 +375,7 @@
<listitem><para>Persistent system spool data, such as printer
or mail queues.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -398,7 +398,7 @@
and similar calls should be used. For further details about this directory, see <ulink
url="https://systemd.io/TEMPORARY_DIRECTORIES">Using /tmp/ and /var/tmp/ Safely</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -421,7 +421,7 @@
special purpose virtual file systems might be mounted below
this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -441,7 +441,7 @@
directories are not world-writable and hence not vulnerable to
security-sensitive name clashes.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -454,7 +454,7 @@
A number of special purpose virtual file systems might be
mounted below this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -466,7 +466,7 @@
files. In sandboxed/containerized setups, this directory is
generally mounted read-only.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -479,7 +479,7 @@
of special purpose virtual file systems might be mounted below
this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -520,7 +520,7 @@
binaries referencing these legacy paths correctly find their
binaries.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -531,7 +531,7 @@
referencing this legacy path correctly find their
resources.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -544,7 +544,7 @@
whose ABI places the dynamic loader in this
path.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -555,7 +555,7 @@
this legacy path correctly find their runtime
data.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>
@ -583,7 +583,7 @@
<varname>$XDG_CACHE_HOME</varname> set, it should use the directory specified in it instead of this
directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -594,7 +594,7 @@
directory be missing. If an application finds <varname>$XDG_CONFIG_HOME</varname> set, it should use
the directory specified in it instead of this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -607,7 +607,7 @@
problematic if the home directory is shared between multiple hosts with different
architectures.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -616,7 +616,7 @@
<listitem><para>Static, private vendor data that is compatible with all
architectures.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -626,7 +626,7 @@
defined on <ulink url="https://wiki.debian.org/Multiarch/Tuples">Multiarch Architecture Specifiers
(Tuples)</ulink> list.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -637,7 +637,7 @@
ensure interoperability. If an application finds <varname>$XDG_DATA_HOME</varname> set, it should use
the directory specified in it instead of this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>

14
man/homectl.xml
View File

@ -139,7 +139,9 @@
<literal>short</literal> all superfluous whitespace is suppressed. If <literal>off</literal> (the
default) the user information is not shown in JSON format but in a friendly human readable formatting
instead. The <option>-j</option> option picks <literal>pretty</literal> when run interactively and
<literal>short</literal> otherwise.</para></listitem>
<literal>short</literal> otherwise.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@ -338,7 +340,7 @@
user, including <option>--email=</option>, <option>--timezone=</option> and
<option>--language=</option>.</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@ -808,7 +810,9 @@
<para>Note that <command>homectl</command> uses bytes for key size, like
<filename>/proc/crypto</filename>, but <citerefentry
project='man-pages'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
uses bits.</para></listitem>
uses bits.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@ -881,7 +885,9 @@
directory of the share. The <option>--cifs-extra-mount-options=</option> setting allows specifying
additional mount options when mounting the share, see <citerefentry
project='man-pages'><refentrytitle>mount.cifs</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for details.</para></listitem>
for details.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>

4
man/hostnamectl.xml
View File

@ -64,7 +64,9 @@
<term><command>status</command></term>
<listitem><para>Show system hostname and related information. If no command is specified,
this is the implied default.</para></listitem>
this is the implied default.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>

252
man/journalctl.xml
View File

@ -123,7 +123,9 @@
<para>Note that <option>--user</option> only works if persistent logging is enabled, via the
<varname>Storage=</varname> setting in
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v205"/></listitem>
</varlistentry>
<varlistentry>
@ -131,7 +133,9 @@
<term><option>--machine=</option></term>
<listitem><para>Show messages from a running, local container. Specify a container name to connect
to.</para></listitem>
to.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -139,7 +143,9 @@
<term><option>--merge</option></term>
<listitem><para>Show entries interleaved from all available journals, including remote
ones.</para></listitem>
ones.</para>
<xi:include href="version-info.xml" xpointer="v190"/></listitem>
</varlistentry>
<varlistentry>
@ -148,7 +154,9 @@
<listitem><para>Takes a directory path as argument. If specified, journalctl will operate on the
specified journal directory <replaceable>DIR</replaceable> instead of the default runtime and system
journal paths.</para></listitem>
journal paths.</para>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
<varlistentry>
@ -157,7 +165,9 @@
<listitem><para>Takes a file glob as an argument. If specified, journalctl will operate on the
specified journal files matching <replaceable>GLOB</replaceable> instead of the default runtime and
system journal paths. May be specified multiple times, in which case files will be suitably
interleaved.</para></listitem>
interleaved.</para>
<xi:include href="version-info.xml" xpointer="v205"/></listitem>
</varlistentry>
<varlistentry>
@ -169,7 +179,9 @@
<filename><replaceable>ROOT</replaceable>/var/lib/systemd/catalog/database</filename>, and journal
files under <filename><replaceable>ROOT</replaceable>/run/journal/</filename> or
<filename><replaceable>ROOT</replaceable>/var/log/journal/</filename> will be displayed).
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -183,7 +195,9 @@
the <ulink url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions
Specification</ulink>. For further information on supported disk images, see
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
switch of the same name.</para></listitem>
switch of the same name.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="image-policy-open" />
@ -197,7 +211,9 @@
shown, interleaved. If the namespace identifier is prefixed with <literal>+</literal> data from the
specified namespace and the default namespace is shown, interleaved, but no other. For details about
journal namespaces see
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para></listitem>
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@ -226,7 +242,9 @@
after the current time, respectively. For complete time and date specification, see
<citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>. Note
that <option>--output=short-full</option> prints timestamps that follow precisely this format.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -234,7 +252,9 @@
<term><option>--cursor=</option></term>
<listitem><para>Start showing entries from the location in the journal specified by the passed
cursor.</para></listitem>
cursor.</para>
<xi:include href="version-info.xml" xpointer="v193"/></listitem>
</varlistentry>
<varlistentry>
@ -242,7 +262,9 @@
<listitem><para>Start showing entries from the location in the journal <emphasis>after</emphasis>
the location specified by the passed cursor. The cursor is shown when the
<option>--show-cursor</option> option is used.</para></listitem>
<option>--show-cursor</option> option is used.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -252,7 +274,9 @@
entries <emphasis>after</emphasis> this location. Otherwise show entries according to the other
given options. At the end, write the cursor of the last entry to
<replaceable>FILE</replaceable>. Use this option to continually read the journal by sequentially
calling <command>journalctl</command>.</para></listitem>
calling <command>journalctl</command>.</para>
<xi:include href="version-info.xml" xpointer="v242"/></listitem>
</varlistentry>
<varlistentry>
@ -281,7 +305,9 @@
logs for the boot given by <replaceable>ID</replaceable> are shown.</para>
<para>The special argument <constant>all</constant> can be used to negate the effect of an earlier
use of <option>-b</option>.</para></listitem>
use of <option>-b</option>.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -302,7 +328,9 @@
<para>With <option>--user</option>, all <option>--unit=</option> arguments will be converted to match
user messages as if specified with <option>--user-unit=</option>.</para>
<para>This parameter can be specified multiple times.</para></listitem>
<para>This parameter can be specified multiple times.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -316,7 +344,9 @@
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>
unit, all logs of children of the unit will be shown.</para>
<para>This parameter can be specified multiple times.</para></listitem>
<para>This parameter can be specified multiple times.</para>
<xi:include href="version-info.xml" xpointer="v198"/></listitem>
</varlistentry>
<varlistentry>
@ -326,7 +356,9 @@
<listitem><para>Show messages for the specified syslog identifier
<replaceable>SYSLOG_IDENTIFIER</replaceable>.</para>
<para>This parameter can be specified multiple times.</para></listitem>
<para>This parameter can be specified multiple times.</para>
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
</varlistentry>
<varlistentry>
@ -344,7 +376,9 @@
messages with this log level or a lower (hence more important) log level are shown. If a range is
specified, all messages within the range are shown, including both the start and the end value of the
range. This will add <literal>PRIORITY=</literal> matches for the specified
priorities.</para></listitem>
priorities.</para>
<xi:include href="version-info.xml" xpointer="v188"/></listitem>
</varlistentry>
<varlistentry>
@ -354,7 +388,9 @@
facility names. The names are the usual syslog facilities as documented in <citerefentry
project='man-pages'><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
<option>--facility=help</option> may be used to display a list of known facility names and exit.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@ -372,13 +408,17 @@
below.</para>
<para>When used with <option>--lines=</option> (not prefixed with <literal>+</literal>),
<option>--reverse</option> is implied.</para></listitem>
<option>--reverse</option> is implied.</para>
<xi:include href="version-info.xml" xpointer="v237"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--case-sensitive<optional>=BOOLEAN</optional></option></term>
<listitem><para>Make pattern matching case sensitive or case insensitive.</para></listitem>
<listitem><para>Make pattern matching case sensitive or case insensitive.</para>
<xi:include href="version-info.xml" xpointer="v237"/></listitem>
</varlistentry>
<varlistentry>
@ -386,7 +426,9 @@
<term><option>--dmesg</option></term>
<listitem><para>Show only kernel messages. This implies <option>-b</option> and adds the match
<literal>_TRANSPORT=kernel</literal>.</para></listitem>
<literal>_TRANSPORT=kernel</literal>.</para>
<xi:include href="version-info.xml" xpointer="v205"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@ -408,7 +450,9 @@
<varlistentry>
<term><option>short</option></term>
<listitem><para>is the default and generates an output that is mostly identical to the
formatting of classic syslog files, showing one line per journal entry.</para></listitem>
formatting of classic syslog files, showing one line per journal entry.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -416,18 +460,24 @@
<listitem><para>is very similar, but shows timestamps in the format the
<option>--since=</option> and <option>--until=</option> options accept. Unlike the timestamp
information shown in <option>short</option> output mode this mode includes weekday, year and
timezone information in the output, and is locale-independent.</para></listitem>
timezone information in the output, and is locale-independent.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
<term><option>short-iso</option></term>
<listitem><para>is very similar, but shows ISO 8601 wallclock timestamps.</para></listitem>
<listitem><para>is very similar, but shows ISO 8601 wallclock timestamps.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
<term><option>short-iso-precise</option></term>
<listitem><para>as for <option>short-iso</option> but includes full microsecond
precision.</para></listitem>
precision.</para>
<xi:include href="version-info.xml" xpointer="v234"/></listitem>
</varlistentry>
<varlistentry>
@ -442,13 +492,17 @@
<varlistentry>
<term><option>short-precise</option></term>
<listitem><para>is very similar, but shows classic syslog timestamps with full microsecond
precision.</para></listitem>
precision.</para>
<xi:include href="version-info.xml" xpointer="v207"/></listitem>
</varlistentry>
<varlistentry>
<term><option>short-monotonic</option></term>
<listitem><para>is very similar, but shows monotonic timestamps instead of wallclock
timestamps.</para></listitem>
timestamps.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -463,12 +517,16 @@
<varlistentry>
<term><option>short-unix</option></term>
<listitem><para>is very similar, but shows seconds passed since January 1st 1970 UTC instead of
wallclock timestamps ("UNIX time"). The time is shown with microsecond accuracy.</para></listitem>
wallclock timestamps ("UNIX time"). The time is shown with microsecond accuracy.</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
<term><option>verbose</option></term>
<listitem><para>shows the full-structured entry items with all fields.</para></listitem>
<listitem><para>shows the full-structured entry items with all fields.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -478,7 +536,9 @@
url="https://systemd.io/JOURNAL_EXPORT_FORMATS#journal-export-format">Journal Export
Format</ulink> for more information). To import the binary stream back into native journald
format use
<citerefentry><refentrytitle>systemd-journal-remote</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para></listitem>
<citerefentry><refentrytitle>systemd-journal-remote</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -499,13 +559,17 @@
containing the raw bytes individually formatted as unsigned numbers.</para></listitem>
</orderedlist>
Note that this encoding is reversible (with the exception of the size limit).</para></listitem>
Note that this encoding is reversible (with the exception of the size limit).</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
<term><option>json-pretty</option></term>
<listitem><para>formats entries as JSON data structures, but formats them in multiple lines in
order to make them more readable by humans.</para></listitem>
order to make them more readable by humans.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -513,7 +577,9 @@
<listitem><para>formats entries as JSON data structures, but wraps them in a format suitable for
<ulink
url="https://developer.mozilla.org/en-US/docs/Server-sent_events/Using_server-sent_events">Server-Sent
Events</ulink>.</para></listitem>
Events</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -521,7 +587,9 @@
<listitem><para>formats entries as JSON data structures, but prefixes them with an ASCII Record
Separator character (0x1E) and suffixes them with an ASCII Line Feed character (0x0A), in
accordance with <ulink url="https://tools.ietf.org/html/rfc7464">JavaScript Object Notation
(JSON) Text Sequences </ulink> (<literal>application/json-seq</literal>).</para></listitem>
(JSON) Text Sequences </ulink> (<literal>application/json-seq</literal>).</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
<varlistentry>
@ -529,14 +597,18 @@
<listitem><para>generates a very terse output, only showing the actual message of each journal
entry with no metadata, not even a timestamp. If combined with the
<option>--output-fields=</option> option will output the listed fields for each log record,
instead of the message.</para></listitem>
instead of the message.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
<term><option>with-unit</option></term>
<listitem><para>similar to <option>short-full</option>, but prefixes the unit and user unit names
instead of the traditional syslog identifier. Useful when using templated instances, as it will
include the arguments in the unit names.</para></listitem>
include the arguments in the unit names.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
</variablelist></listitem>
</varlistentry>
@ -550,7 +622,9 @@
<option>json-pretty</option>, <option>json-sse</option> and <option>json-seq</option>), as well as
on <option>cat</option>. For the former, the <literal>__CURSOR</literal>,
<literal>__REALTIME_TIMESTAMP</literal>, <literal>__MONOTONIC_TIMESTAMP</literal>, and
<literal>_BOOT_ID</literal> fields are always printed.</para></listitem>
<literal>_BOOT_ID</literal> fields are always printed.</para>
<xi:include href="version-info.xml" xpointer="v236"/></listitem>
</varlistentry>
<varlistentry>
@ -570,7 +644,9 @@
<term><option>-r</option></term>
<term><option>--reverse</option></term>
<listitem><para>Reverse output so that the newest entries are displayed first.</para></listitem>
<listitem><para>Reverse output so that the newest entries are displayed first.</para>
<xi:include href="version-info.xml" xpointer="v198"/></listitem>
</varlistentry>
<varlistentry>
@ -578,13 +654,17 @@
<listitem><para>The cursor is shown after the last entry after two dashes:</para>
<programlisting>-- cursor: s=0639…</programlisting>
<para>The format of the cursor is private and subject to change.</para></listitem>
<para>The format of the cursor is private and subject to change.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--utc</option></term>
<listitem><para>Express time in Coordinated Universal Time (UTC).</para></listitem>
<listitem><para>Express time in Coordinated Universal Time (UTC).</para>
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
</varlistentry>
<varlistentry>
@ -600,7 +680,9 @@
Catalog Developer Documentation</ulink>.</para>
<para>Note: when attaching <command>journalctl</command> output to bug reports, please do
<emphasis>not</emphasis> use <option>-x</option>.</para></listitem>
<emphasis>not</emphasis> use <option>-x</option>.</para>
<xi:include href="version-info.xml" xpointer="v196"/></listitem>
</varlistentry>
<varlistentry>
@ -610,7 +692,9 @@
switch has an effect only on the <option>short</option> family of output modes (see above).</para>
<para>Note: this option does not remove occurrences of the hostname from log entries themselves, so
it does not prevent the hostname from being visible in the logs.</para></listitem>
it does not prevent the hostname from being visible in the logs.</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@ -622,7 +706,9 @@
full fields, allowing them to wrap or be truncated by the pager, if one is used.</para>
<para>The old options <option>-l</option>/<option>--full</option> are not useful anymore, except to
undo <option>--no-full</option>.</para></listitem>
undo <option>--no-full</option>.</para>
<xi:include href="version-info.xml" xpointer="v196"/></listitem>
</varlistentry>
<varlistentry>
@ -679,7 +765,9 @@
while <option>-nall</option> will disable this cap. Note that this option is only supported for
the <citerefentry
project='man-pages'><refentrytitle>less</refentrytitle><manvolnum>1</manvolnum></citerefentry>
pager.</para></listitem>
pager.</para>
<xi:include href="version-info.xml" xpointer="v198"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@ -696,21 +784,27 @@
<listitem><para>Specifies the change interval for the sealing key when generating an FSS key pair
with <option>--setup-keys</option>. Shorter intervals increase CPU consumption but shorten the time
range of undetectable journal alterations. Defaults to 15min.</para></listitem>
range of undetectable journal alterations. Defaults to 15min.</para>
<xi:include href="version-info.xml" xpointer="v189"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--verify-key=</option></term>
<listitem><para>Specifies the FSS verification key to use for the <option>--verify</option>
operation.</para></listitem>
operation.</para>
<xi:include href="version-info.xml" xpointer="v189"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--force</option></term>
<listitem><para>When <option>--setup-keys</option> is passed and Forward Secure Sealing (FSS) has
already been configured, recreate FSS keys.</para></listitem>
already been configured, recreate FSS keys.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@ -725,7 +819,9 @@
<term><option>-N</option></term>
<term><option>--fields</option></term>
<listitem><para>Print all field names currently used in all entries of the journal.</para></listitem>
<listitem><para>Print all field names currently used in all entries of the journal.</para>
<xi:include href="version-info.xml" xpointer="v229"/></listitem>
</varlistentry>
<varlistentry>
@ -733,21 +829,27 @@
<term><option>--field=</option></term>
<listitem><para>Print all possible data values the specified field can take in all entries of the
journal.</para></listitem>
journal.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--list-boots</option></term>
<listitem><para>Show a tabular list of boot numbers (relative to the current boot), their IDs, and
the timestamps of the first and last message pertaining to the boot.</para></listitem>
the timestamps of the first and last message pertaining to the boot.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--disk-usage</option></term>
<listitem><para>Shows the current disk usage of all journal files. This shows the sum of the disk
usage of all archived and active journal files.</para></listitem>
usage of all archived and active journal files.</para>
<xi:include href="version-info.xml" xpointer="v190"/></listitem>
</varlistentry>
<varlistentry>
@ -786,7 +888,9 @@
so, all active files are rotated first, and the requested vacuuming operation is executed right
after. The rotation has the effect that all currently active files are archived (and potentially new,
empty journal files opened as replacement), and hence the vacuuming operation has the greatest effect
as it can take all log data written so far into account.</para></listitem>
as it can take all log data written so far into account.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@ -794,7 +898,9 @@
<listitem><para>Check the journal file for internal consistency. If the file has been generated
with FSS enabled and the FSS verification key has been specified with
<option>--verify-key=</option>, authenticity of the journal file is verified.</para></listitem>
<option>--verify-key=</option>, authenticity of the journal file is verified.</para>
<xi:include href="version-info.xml" xpointer="v189"/></listitem>
</varlistentry>
<varlistentry>
@ -803,7 +909,9 @@
<listitem><para>Asks the journal daemon to write all yet unwritten journal data to the backing file
system and synchronize all journals. This call does not return until the synchronization operation
is complete. This command guarantees that any log messages written before its invocation are safely
stored on disk at the time it returns.</para></listitem>
stored on disk at the time it returns.</para>
<xi:include href="version-info.xml" xpointer="v228"/></listitem>
</varlistentry>
<varlistentry>
@ -813,7 +921,9 @@
requested the daemon will write further log data to <filename>/run/log/journal/</filename> and
stops writing to <filename>/var/log/journal/</filename>. A subsequent call to
<option>--flush</option> causes the log output to switch back to
<filename>/var/log/journal/</filename>, see above.</para></listitem>
<filename>/var/log/journal/</filename>, see above.</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
<varlistentry>
@ -823,7 +933,9 @@
file system and <filename>/var/log/journal/</filename> reside on the same mount point. This operation
is used during system shutdown in order to make the journal daemon stop writing data to
<filename>/var/log/journal/</filename> in case that directory is located on a mount point that needs
to be unmounted.</para></listitem>
to be unmounted.</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
<varlistentry>
@ -836,7 +948,9 @@
<filename>/var/log/journal/</filename> once during system runtime (but see
<option>--relinquish-var</option> below), and this command exits cleanly without executing any
operation if this has already happened. This command effectively guarantees that all data is flushed
to <filename>/var/log/journal/</filename> at the time it returns.</para></listitem>
to <filename>/var/log/journal/</filename> at the time it returns.</para>
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
</varlistentry>
<varlistentry>
@ -847,7 +961,9 @@
journal files are marked as archived and renamed, so that they are never written to in future. New
(empty) journal files are then created in their place. This operation may be combined with
<option>--vacuum-size=</option>, <option>--vacuum-time=</option> and
<option>--vacuum-file=</option> into a single command, see above.</para></listitem>
<option>--vacuum-file=</option> into a single command, see above.</para>
<xi:include href="version-info.xml" xpointer="v227"/></listitem>
</varlistentry>
<varlistentry>
@ -857,7 +973,9 @@
journal fields accessed.</para>
<para>This option is particularly useful when trying to identify out-of-order journal entries, as
happens for example when the machine is booted with the wrong system time.</para></listitem>
happens for example when the machine is booted with the wrong system time.</para>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
<varlistentry>
@ -867,7 +985,9 @@
short description strings.</para>
<para>If any <replaceable>128-bit-ID</replaceable>s are specified, only those entries are
shown.</para></listitem>
shown.</para>
<xi:include href="version-info.xml" xpointer="v196"/></listitem>
</varlistentry>
<varlistentry>
@ -878,7 +998,9 @@
files).</para>
<para>If any <replaceable>128-bit-ID</replaceable>s are specified, only those entries are
shown.</para></listitem>
shown.</para>
<xi:include href="version-info.xml" xpointer="v199"/></listitem>
</varlistentry>
<varlistentry>
@ -886,7 +1008,9 @@
<listitem><para>Update the message catalog index. This command needs to be executed each time new
catalog files are installed, removed, or updated to rebuild the binary catalog
index.</para></listitem>
index.</para>
<xi:include href="version-info.xml" xpointer="v196"/></listitem>
</varlistentry>
<varlistentry>
@ -898,7 +1022,9 @@
externally. Refer to the <option>Seal=</option> option in
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
information on Forward Secure Sealing and for a link to a refereed scholarly paper detailing the
cryptographic theory it is based on.</para></listitem>
cryptographic theory it is based on.</para>
<xi:include href="version-info.xml" xpointer="v189"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="help" />

2
man/journald.conf.xml
View File

@ -424,6 +424,8 @@
<literal>systemd.journald.max_level_kmsg=</literal>,
<literal>systemd.journald.max_level_console=</literal>,
<literal>systemd.journald.max_level_wall=</literal>.</para>
<xi:include href="version-info.xml" xpointer="v185"/>
</listitem>
</varlistentry>

24
man/kernel-command-line.xml
View File

@ -80,6 +80,8 @@
<para>Parameters understood by the system and service
manager to control system behavior. For details, see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -92,6 +94,8 @@
<citerefentry><refentrytitle>systemd-debug-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
to mask or start specific units at boot, or invoke a debug
shell on tty9.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -204,6 +208,8 @@
<para>Parameters understood by the system and service
manager, as compatibility and convenience options. For details, see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -240,6 +246,8 @@
<para>Parameters understood by the file system checker
services. For details, see
<citerefentry><refentrytitle>systemd-fsck@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -265,6 +273,8 @@
<para>Parameters understood by the journal service. For
details, see
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -278,6 +288,8 @@
<listitem>
<para>Parameters understood by the virtual console setup logic. For details, see
<citerefentry><refentrytitle>vconsole.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -301,6 +313,8 @@
<para>Parameters understood by the device event managing
daemon. For details, see
<citerefentry><refentrytitle>systemd-udevd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -334,6 +348,8 @@
<para>Configures the LUKS full-disk encryption logic at
boot. For details, see
<citerefentry><refentrytitle>systemd-cryptsetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -368,6 +384,8 @@
will be in effect. In this case <varname>rootfstype=</varname>, <varname>rootflags=</varname>,
<varname>ro</varname>, <varname>rw</varname> will be interpreted by
<command>systemd-gpt-auto-generator</command>.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -402,6 +420,8 @@
<para>Configures the integrity protection root hash for the root and <filename>/usr</filename> file systems, and other related
parameters. For details, see
<citerefentry><refentrytitle>systemd-veritysetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
@ -540,7 +560,7 @@
details, see
<citerefentry><refentrytitle>systemd-modules-load.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
<xi:include href="version-info.xml" xpointer="v187"/>
</listitem>
</varlistentry>
@ -565,6 +585,8 @@
<citerefentry project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>-like
paths are supported. For details, see
<citerefentry><refentrytitle>systemd-hibernate-resume-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v217"/>
</listitem>
</varlistentry>

14
man/kernel-install.xml
View File

@ -139,7 +139,7 @@
<para>If <varname>$KERNEL_INSTALL_LAYOUT</varname> is not "uki", this plugin does nothing.</para></listitem>
</itemizedlist>
<xi:include href="version-info.xml" xpointer="v241"/>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>
@ -172,7 +172,7 @@
</para></listitem>
</itemizedlist>
<xi:include href="version-info.xml" xpointer="v203"/>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>
@ -182,7 +182,7 @@
values of the various <varname>$KERNEL_INSTALL_*</varname> environment variables listed
below.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
<xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
</varlistentry>
@ -337,6 +337,8 @@
kernel and initrds under
<filename>$BOOT/<replaceable>ENTRY-TOKEN</replaceable>/<replaceable>KERNEL-VERSION</replaceable>/</filename></para>
<para>Implemented by <filename>90-loaderentry.install</filename>.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
@ -357,6 +359,8 @@
<term>other</term>
<listitem>
<para>Some other layout not understood natively by <command>kernel-install</command>.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
@ -441,7 +445,7 @@
exist, <filename>/proc/cmdline</filename> is used. <varname>$KERNEL_INSTALL_CONF_ROOT</varname>
may be used to override the path.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>
@ -497,7 +501,7 @@
If available, <varname>PRETTY_NAME=</varname> is read from these files and used as the title of the boot menu entry.
Otherwise, <literal>Linux <replaceable>KERNEL-VERSION</replaceable></literal> will be used.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>

26
man/localectl.xml
View File

@ -71,7 +71,9 @@
<term><command>status</command></term>
<listitem><para>Show current settings of the system locale and keyboard mapping.
If no command is specified, this is the implied default.</para></listitem>
If no command is specified, this is the implied default.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -86,7 +88,7 @@
<command>list-locales</command> for a list of available
locales (see below). </para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -94,7 +96,9 @@
<listitem><para>List available locales useful for
configuration with
<command>set-locale</command>.</para></listitem>
<command>set-locale</command>.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -108,7 +112,9 @@
keyboard mapping of X11, after converting it to the closest
matching X11 keyboard mapping. Use
<command>list-keymaps</command> for a list of available
keyboard mappings (see below).</para></listitem>
keyboard mappings (see below).</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -116,7 +122,9 @@
<listitem><para>List available keyboard mappings for the
console, useful for configuration with
<command>set-keymap</command>.</para></listitem>
<command>set-keymap</command>.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -130,7 +138,9 @@
for details. Unless <option>--no-convert</option> is passed,
the selected setting is also applied as the system console
keyboard mapping, after converting it to the closest matching
console keyboard mapping.</para></listitem>
console keyboard mapping.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -144,7 +154,9 @@
<command>set-keymap</command>. The command
<command>list-x11-keymap-variants</command> optionally takes a
layout parameter to limit the output to the variants suitable
for the specific layout.</para></listitem>
for the specific layout.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
</variablelist>

6
man/loginctl.xml
View File

@ -115,7 +115,9 @@
<term><command>unlock-sessions</command></term>
<listitem><para>Activates/deactivates the screen lock on all
current sessions supporting it. </para></listitem>
current sessions supporting it. </para>
<xi:include href="version-info.xml" xpointer="v188"/></listitem>
</varlistentry>
<varlistentry>
@ -348,6 +350,8 @@
<term><option>--full</option></term>
<listitem><para>Do not ellipsize process tree entries.</para>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>

8
man/logind.conf.xml
View File

@ -251,7 +251,9 @@
to take over suspend and hibernation handling, and to use their own configuration
mechanisms. If a low-level inhibitor lock is taken, logind will not take any
action when that key or switch is triggered and the <varname>Handle*=</varname>
settings are irrelevant.</para></listitem>
settings are irrelevant.</para>
<xi:include href="version-info.xml" xpointer="v184"/></listitem>
</varlistentry>
<varlistentry>
@ -280,7 +282,9 @@
This means that when <command>systemd-logind</command> is handling events by
itself (no low level inhibitor locks are taken by another application), the lid
switch does not respect suspend blockers by default, but the power and sleep keys
do.</para></listitem>
do.</para>
<xi:include href="version-info.xml" xpointer="v190"/></listitem>
</varlistentry>
<varlistentry>

40
man/machinectl.xml
View File

@ -97,7 +97,9 @@
be started, use <command>list-images</command> (see
below). Note that this command hides the special
<literal>.host</literal> machine by default. Use the
<option>--all</option> switch to show it.</para></listitem>
<option>--all</option> switch to show it.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -113,7 +115,7 @@
console output of the machine, but not necessarily journal
contents of the machine itself.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -127,7 +129,7 @@
required, and does not print the control group tree or journal entries. Use <command>status</command> if you
are looking for formatted human-readable output.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -161,7 +163,7 @@
<command>systemd-nspawn</command> directly. To stop a running
container use <command>machinectl poweroff</command>.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -188,7 +190,7 @@
a single command, either interactively or in the
background.</para>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -233,7 +235,7 @@
preferable for scripting purposes. However, note that <command>systemd-run</command> might require
higher privileges than <command>machinectl shell</command>.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
</varlistentry>
<varlistentry>
@ -250,7 +252,7 @@
Note that this command does not implicitly start or power off the containers that are being operated on.
If this is desired, combine the command with the <option>--now</option> switch.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -267,7 +269,7 @@
terminate a container or VM, without cleanly shutting it
down.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v212"/></listitem>
</varlistentry>
<varlistentry>
@ -279,7 +281,7 @@
on a non-containerized system, and is compatible with
containers running any system manager.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -292,7 +294,7 @@
<command>poweroff</command> to issue a clean shutdown
request.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -305,7 +307,7 @@
process to kill. Use <option>--signal=</option> to select the
signal to send.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -338,7 +340,7 @@
group ID is preserved for the copy, otherwise all files and directories in the copy will be owned by the root
user and group (UID/GID 0).</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -354,7 +356,7 @@
group ID is preserved for the copy, otherwise all files and directories in the copy will be owned by the root
user and group (UID/GID 0).</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
</variablelist></refsect2>
@ -387,7 +389,7 @@
<command>show-image</command> (see below) to generate
computer-parsable output instead.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -405,7 +407,7 @@
<command>image-status</command> if you are looking for
formatted human-readable output.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -477,7 +479,7 @@
the host's own directory tree, may not be
removed.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -705,7 +707,7 @@
transfers and their IDs, use
<command>list-transfers</command>. </para>
<xi:include href="version-info.xml" xpointer="v237"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
</variablelist></refsect2>
@ -780,7 +782,7 @@
processes of the machine. If omitted, defaults to
<option>all</option>.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="signal" />
@ -809,7 +811,7 @@
<para>Note that this option is not supported for the <command>login</command> command.
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>

18
man/networkctl.xml
View File

@ -209,7 +209,7 @@
</variablelist>
</para>
<xi:include href="version-info.xml" xpointer="v242"/>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
@ -278,7 +278,7 @@
</variablelist>
</para>
<xi:include href="version-info.xml" xpointer="v242"/>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
@ -308,7 +308,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
1 neighbors listed.</programlisting></para>
<xi:include href="version-info.xml" xpointer="v242"/>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
@ -347,7 +347,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
</term>
<listitem><para>Deletes virtual netdevs. Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
<varlistentry>
@ -357,7 +357,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
</term>
<listitem><para>Bring devices up. Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@ -367,7 +367,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
</term>
<listitem><para>Bring devices down. Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@ -378,7 +378,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
<listitem><para>Renew dynamic configurations e.g. addresses received from DHCP server.
Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
<varlistentry>
@ -389,7 +389,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
<listitem><para>Send a FORCERENEW message to all connected clients, triggering DHCP reconfiguration.
Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@ -402,7 +402,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
corresponding to the specified interface. So, if you edit config files, it is necessary to call
<command>networkctl reload</command> first to apply new settings.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
<varlistentry>

18
man/networkd.conf.xml
View File

@ -147,7 +147,9 @@
<literal>43793</literal> as the vendor identifier (systemd) and hashed contents of
<citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
This is the default if <varname>DUIDType=</varname> is not specified.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@ -158,7 +160,9 @@
<citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>
is used as a DUID value. About the application-specific machine ID, see
<citerefentry><refentrytitle>sd_id128_get_machine_app_specific</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@ -168,13 +172,17 @@
then the MAC address of the interface is used as a DUID value. The value <literal>link-layer-time</literal>
can take additional time value after a colon, e.g. <literal>link-layer-time:2018-01-23 12:34:56 UTC</literal>.
The default time value is <literal>2000-01-01 00:00:00 UTC</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
</variablelist>
</para>
<para>In all cases, <varname>DUIDRawData=</varname> can be used to override the
actual DUID value that is used.</para></listitem>
actual DUID value that is used.</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@ -203,6 +211,8 @@ DUIDRawData=00:00:ab:11:f9:2a:c2:77:29:f9:5c:00</programlisting>
43793 (<literal>00:00:ab:11</literal>), and identifier value <literal>f9:2a:c2:77:29:f9:5c:00</literal>.
</para>
</example>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
</variablelist>

4
man/oomd.conf.xml
View File

@ -58,7 +58,7 @@
<varname>ManagedOOMSwap=</varname>. Takes a value specified in percent (when suffixed with "%"),
permille ("‰") or permyriad ("‱"), between 0% and 100%, inclusive. Defaults to 90%.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
</varlistentry>
<varlistentry>
@ -76,7 +76,7 @@
<varname>ManagedOOMMemoryPressure=</varname>. Takes a fraction specified in the same way as
<varname>SwapUsedLimit=</varname> above. Defaults to 60%.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
</varlistentry>
<varlistentry>

28
man/os-release.xml
View File

@ -215,7 +215,9 @@
Edition"</literal>.</para>
<para>Note: this field is for display purposes only. The <varname>VARIANT_ID</varname> field should
be used for making programmatic decisions.</para></listitem>
be used for making programmatic decisions.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
@ -227,7 +229,9 @@
may not be implemented on all systems.</para>
<para>Examples: <literal>VARIANT_ID=server</literal>, <literal>VARIANT_ID=embedded</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
</variablelist>
</refsect2>
@ -268,7 +272,9 @@
is optional and may not be implemented on all systems.</para>
<para>Examples: <literal>VERSION_CODENAME=buster</literal>,
<literal>VERSION_CODENAME=xenial</literal>.</para></listitem>
<literal>VERSION_CODENAME=xenial</literal>.</para>
<xi:include href="version-info.xml" xpointer="v231"/></listitem>
</varlistentry>
<varlistentry>
@ -283,7 +289,9 @@
optional.</para>
<para>Examples: <literal>BUILD_ID="2013-03-20.3"</literal>, <literal>BUILD_ID=201303203</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v200"/></listitem>
</varlistentry>
<varlistentry>
@ -384,7 +392,9 @@
systems.</para>
<para>Examples: <literal>LOGO=fedora-logo</literal>, <literal>LOGO=distributor-logo-opensuse</literal>
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
<varlistentry>
@ -452,7 +462,9 @@
<para>See <citerefentry><refentrytitle>org.freedesktop.hostname1</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for a description of how
<citerefentry><refentrytitle>systemd-hostnamed.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
determines the fallback hostname.</para></listitem>
determines the fallback hostname.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
@ -480,7 +492,9 @@
for more information.</para>
<para>Examples: <literal>SYSEXT_LEVEL=2</literal>, <literal>SYSEXT_LEVEL=15.14</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>

10
man/pam_systemd.xml
View File

@ -299,7 +299,7 @@
<listitem><para>Sets unit <varname>MemoryMax=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -307,7 +307,7 @@
<listitem><para>Sets unit <varname>TasksMax=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -315,7 +315,7 @@
<listitem><para>Sets unit <varname>CPUWeight=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -323,7 +323,7 @@
<listitem><para>Sets unit <varname>IOWeight=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -331,7 +331,7 @@
<listitem><para>Sets unit <varname>RuntimeMaxSec=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
</variablelist>

2
man/portablectl.xml
View File

@ -155,7 +155,7 @@
files. This is a convenience feature to allow all arguments passed as <command>attach</command> also to
<command>detach</command>.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<para>If <option>--now</option> and/or <option>--enable</option> are passed, the portable services are
immediately stopped (blocking operation) and/or disabled before detaching the image. Prefix(es) are also accepted,

2
man/resolvectl.xml
View File

@ -203,6 +203,8 @@
<para>For details about these settings, their possible values and their effect, see the
corresponding settings in
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>

54
man/systemctl.xml
View File

@ -171,6 +171,8 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</para>
<para>Also see <option>--show-types</option>, <option>--all</option>, and <option>--state=</option>.</para>
<xi:include href="version-info.xml" xpointer="v202"/>
</listitem>
</varlistentry>
@ -198,6 +200,8 @@ Sun 2017-02-26 20:57:49 EST 2h 3min left Sun 2017-02-26 11:56:36 EST 6h ago
<para><emphasis>ACTIVATES</emphasis> shows the name the service the timer activates when it runs.</para>
<para>Also see <option>--all</option> and <option>--state=</option>.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@ -224,6 +228,8 @@ Sun 2017-02-26 20:57:49 EST 2h 3min left Sun 2017-02-26 11:56:36 EST 6h ago
non-zero otherwise. Unless <option>--quiet</option> is
specified, this will also print the current unit state to
standard output.</para>
<xi:include href="version-info.xml" xpointer="v197"/>
</listitem>
</varlistentry>
@ -349,6 +355,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
understanding of these units if any unit files were
updated on disk and the <command>daemon-reload</command>
command wasn't issued since.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@ -359,6 +367,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<para>Show manual pages for one or more units, if
available. If a PID is given, the manual pages for the unit
the process belongs to are shown.</para>
<xi:include href="version-info.xml" xpointer="v185"/>
</listitem>
</varlistentry>
@ -393,6 +403,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<para>Note that this command only lists units currently loaded into memory by the service manager. In
particular, this command is not suitable to get a comprehensive list at all reverse dependencies on a
specific unit, as it won't list the dependencies declared by units currently not loaded.</para>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
@ -497,6 +509,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
nothing if the units are not running.</para>
<!-- Note that we don't document force-reload here, as that is just compatibility support, and we generally
don't document that. -->
<xi:include href="version-info.xml" xpointer="v229"/>
</listitem>
</varlistentry>
<varlistentry>
@ -551,6 +565,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
not specified, the cache and runtime data as well as the file descriptor store are removed (as
these three types of resources are generally redundant and reproducible on the next invocation of
the unit). Note that the specified units must be stopped to invoke this operation.</para>
<xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<varlistentry>
@ -564,6 +580,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
to be suspended. Being suspended means that unit's processes won't be scheduled to run on CPU until thawed.
Note that this command is supported only on systems that use unified cgroup hierarchy. Unit is automatically
thawed just before we execute a job against the unit, e.g. before the unit is stopped.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
@ -575,6 +593,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<para>This is the inverse operation to the <command>freeze</command> command and resumes the execution of
processes in the unit's cgroup.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
@ -609,6 +629,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
property to its defaults.</para>
<para>Example: <command>systemctl set-property avahi-daemon.service IPAddressDeny=</command></para>
<xi:include href="version-info.xml" xpointer="v206"/>
</listitem>
</varlistentry>
@ -1109,7 +1131,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
edit</command>, <command>systemctl set-property</command> and <command>systemctl mask</command> and puts
the original unit file with its settings back in effect.</para>
<xi:include href="version-info.xml" xpointer="v238"/>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -1129,7 +1151,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<option>--global</option> in a way similar to
<command>enable</command>.</para>
<xi:include href="version-info.xml" xpointer="v238"/>
<xi:include href="version-info.xml" xpointer="v217"/>
</listitem>
</varlistentry>
@ -1175,7 +1197,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<filename>/etc/</filename>, since they take precedence over
<filename>/run/</filename>.</para>
<xi:include href="version-info.xml" xpointer="v238"/>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@ -1186,6 +1208,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<para>Return the default target to boot into. This returns
the target unit name <filename>default.target</filename>
is aliased (symlinked) to.</para>
<xi:include href="version-info.xml" xpointer="v205"/>
</listitem>
</varlistentry>
@ -1197,7 +1221,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
(symlinks) the <filename>default.target</filename> alias
to the given target unit.</para>
<xi:include href="version-info.xml" xpointer="v238"/>
<xi:include href="version-info.xml" xpointer="v205"/>
</listitem>
</varlistentry>
@ -1218,7 +1242,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
containers matching one of them are shown.
</para>
<xi:include href="version-info.xml" xpointer="v233"/>
<xi:include href="version-info.xml" xpointer="v212"/>
</listitem>
</varlistentry>
</variablelist>
@ -1341,7 +1365,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
are only meant for processes which are descendants of the shell. Such variables in the global
environment block are confusing to other processes.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
</variablelist>
@ -1724,6 +1748,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<para>Hibernate and suspend the system. This will trigger activation of the special target unit
<filename>hybrid-sleep.target</filename>. This command is asynchronous, and will return after the hybrid
sleep operation is successfully enqueued. It will not wait for the sleep/wake-up cycle to complete.</para>
<xi:include href="version-info.xml" xpointer="v196"/>
</listitem>
</varlistentry>
@ -1951,6 +1977,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<para>When passed to the <command>list-jobs</command> command, for each printed job show which other jobs are
waiting for it. May be combined with <option>--before</option> to show both the jobs waiting for each job as
well as all jobs each job is waiting for.</para>
<xi:include href="version-info.xml" xpointer="v203"/>
</listitem>
</varlistentry>
@ -2156,6 +2184,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<listitem>
<para>Shortcut for <option>--check-inhibitors=no</option>.</para>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
@ -2538,7 +2568,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
menu timeout. Pass zero in order to disable the menu timeout. Note that not all boot loaders
support this functionality.</para>
<xi:include href="version-info.xml" xpointer="v251"/>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@ -2551,7 +2581,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
as argument, or <literal>help</literal> in order to list available entries. Note that not all boot
loaders support this functionality.</para>
<xi:include href="version-info.xml" xpointer="v251"/>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@ -2609,7 +2639,9 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<varlistentry>
<term><option>us</option></term>
<term><option>μs</option></term>
<listitem><para><literal>Day YYYY-MM-DD HH:MM:SS.UUUUUU TZ</literal></para></listitem>
<listitem><para><literal>Day YYYY-MM-DD HH:MM:SS.UUUUUU TZ</literal></para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
</variablelist>
@ -2626,7 +2658,9 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<varlistentry>
<term><option>us+utc</option></term>
<term><option>μs+utc</option></term>
<listitem><para><literal>Day YYYY-MM-DD HH:MM:SS.UUUUUU UTC</literal></para></listitem>
<listitem><para><literal>Day YYYY-MM-DD HH:MM:SS.UUUUUU UTC</literal></para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
</variablelist>

4
man/systemd-ask-password.xml
View File

@ -181,7 +181,9 @@
<term><option>--echo</option></term>
<term><option>-e</option></term>
<listitem><para>Equivalent to <option>--echo=yes</option>, see above.</para></listitem>
<listitem><para>Equivalent to <option>--echo=yes</option>, see above.</para>
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
</varlistentry>
<varlistentry>

18
man/systemd-boot.xml
View File

@ -141,7 +141,7 @@
<term><keycap>→</keycap> (Right)</term>
<listitem><para>Boot selected entry</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -199,7 +199,9 @@
<term><keycap>h</keycap></term>
<term><keycap>?</keycap></term>
<term><keycap>F1</keycap></term>
<listitem><para>Show a help screen</para></listitem>
<listitem><para>Show a help screen</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -304,14 +306,16 @@
<varlistentry>
<term><keycap>Esc</keycap></term>
<term><keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo></term>
<listitem><para>Abort the edit and quit the editor</para></listitem>
<listitem><para>Abort the edit and quit the editor</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><keycombo><keycap>Ctrl</keycap><keycap>k</keycap></keycombo></term>
<listitem><para>Clear the command line forwards</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -319,13 +323,15 @@
<term><keycombo><keycap>Alt</keycap><keycap>Backspace</keycap></keycombo></term>
<listitem><para>Delete word backwards</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><keycombo><keycap>Ctrl</keycap><keycap>Del</keycap></keycombo></term>
<term><keycombo><keycap>Alt</keycap><keycap>d</keycap></keycombo></term>
<listitem><para>Delete word forwards</para></listitem>
<listitem><para>Delete word forwards</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>

14
man/systemd-cgls.xml
View File

@ -71,6 +71,8 @@
<term><option>--full</option></term>
<listitem><para>Do not ellipsize process tree members.</para>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
@ -106,7 +108,9 @@
<listitem><para>Limit control groups shown to the part
corresponding to the container
<replaceable>MACHINE</replaceable>.</para></listitem>
<replaceable>MACHINE</replaceable>.</para>
<xi:include href="version-info.xml" xpointer="v203"/></listitem>
</varlistentry>
<varlistentry>
@ -115,7 +119,9 @@
<listitem><para>Controls whether to include information about extended attributes of the listed
control groups in the output. With the long option, expects a boolean value. Defaults to no.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
@ -123,7 +129,9 @@
<term><option>--cgroup-id=</option></term>
<listitem><para>Controls whether to include the numeric ID of the listed control groups in the
output. With the long option, expects a boolean value. Defaults to no.</para></listitem>
output. With the long option, expects a boolean value. Defaults to no.</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="help" />

8
man/systemd-escape.xml
View File

@ -107,7 +107,9 @@
<listitem><para>Instead of escaping the specified strings,
undo the escaping, reversing the operation. May not be used in
conjunction with <option>--suffix=</option> or
<option>--mangle</option>.</para></listitem>
<option>--mangle</option>.</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
<varlistentry>
@ -119,7 +121,9 @@
possibly automatically append an appropriate unit type suffix
to the string. May not be used in conjunction with
<option>--suffix=</option>, <option>--template=</option> or
<option>--unescape</option>.</para></listitem>
<option>--unescape</option>.</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
<varlistentry>

12
man/systemd-firstboot.xml
View File

@ -202,7 +202,9 @@
for more information on the format of the hashed password. Note that it is not recommended to specify
plaintext passwords on the command line, as other users might be able to see them simply by invoking
<citerefentry project='die-net'><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
<varlistentry>
@ -237,7 +239,9 @@
<listitem><para>Prompt the user interactively for a specific
basic setting. Note that any explicit configuration settings
specified on the command line take precedence, and the user is
not prompted for it.</para></listitem>
not prompted for it.</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
<varlistentry>
@ -265,7 +269,9 @@
<listitem><para>Copy a specific basic setting from the host.
This only works in combination with <option>--root=</option> or <option>--image=</option>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
<varlistentry>

2
man/systemd-fstab-generator.xml
View File

@ -257,7 +257,7 @@
any swap devices configured in <filename>/etc/fstab</filename>.
Defaults to enabled.</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>

4
man/systemd-gpt-auto-generator.xml
View File

@ -279,7 +279,9 @@
logic.</para>
<para>The <varname>rootfstype=</varname> and <varname>rootflags=</varname> are used to select the
file system type and options when the root file system is automatically discovered.</para></listitem>
file system type and options when the root file system is automatically discovered.</para>
<xi:include href="version-info.xml" xpointer="v242"/></listitem>
</varlistentry>
<varlistentry>

4
man/systemd-journal-gatewayd.service.xml
View File

@ -176,7 +176,7 @@
<para>GET parameters can be used to modify what events are
returned. Supported parameters are described below.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
<xi:include href="version-info.xml" xpointer="v197"/>
</listitem>
</varlistentry>
@ -329,7 +329,7 @@
<listitem><para>Match journal fields. See
<citerefentry><refentrytitle>systemd.journal-fields</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v198"/>
<xi:include href="version-info.xml" xpointer="v197"/>
</listitem>
</varlistentry>
</variablelist>

2
man/systemd-journald.service.xml
View File

@ -240,6 +240,8 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
<para>See
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for information about these settings.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>

2
man/systemd-machine-id-setup.xml
View File

@ -87,7 +87,7 @@
given alternate <replaceable>root</replaceable> path, including the path for
<filename>/etc/machine-id</filename> itself.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
<xi:include href="version-info.xml" xpointer="v212"/></listitem>
</varlistentry>
<varlistentry>

4
man/systemd-measure.xml
View File

@ -126,7 +126,9 @@
configures the files to read the unified kernel image components from. Each option corresponds with
the equally named section in the unified kernel PE file. The <option>--linux=</option> switch expects
the path to the ELF kernel file that the unified PE kernel will wrap. All switches except
<option>--linux=</option> are optional. Each option may be used at most once.</para></listitem>
<option>--linux=</option> are optional. Each option may be used at most once.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>

2
man/systemd-modules-load.service.xml
View File

@ -56,7 +56,7 @@
<listitem><para>Takes a comma-separated list of kernel modules to statically load during early boot.
The option prefixed with <literal>rd.</literal> is read in the initrd only.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
</variablelist>

2
man/systemd-mount.xml
View File

@ -272,7 +272,7 @@
<option>--discover</option>, see above), and the file system block device is detected to be removable, this
option is implied.</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>

2
man/systemd-network-generator.service.xml
View File

@ -72,6 +72,8 @@
<listitem>
<para>— translated into
<citerefentry><refentrytitle>systemd.link</refentrytitle><manvolnum>5</manvolnum></citerefentry> files.</para>
<xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>

8
man/systemd-networkd-wait-online.service.xml
View File

@ -76,7 +76,7 @@
<filename>.network</filename> file is used if present, and <literal>degraded</literal> otherwise.
</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
<xi:include href="version-info.xml" xpointer="v213"/></listitem>
</varlistentry>
<varlistentry>
@ -87,7 +87,7 @@
interface is ignored. This option may be used more than once
to ignore multiple network interfaces. </para>
<xi:include href="version-info.xml" xpointer="v242"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -101,7 +101,7 @@
But this does not override operational states specified in <option>--interface=</option> option.
</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
<xi:include href="version-info.xml" xpointer="v242"/></listitem>
</varlistentry>
<varlistentry>
@ -164,7 +164,7 @@
by the time the timeout elapses. A timeout of 0 disables the
timeout. Defaults to 120 seconds. </para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>

156
man/systemd-nspawn.xml
View File

@ -244,7 +244,9 @@
<para>Note that this switch leaves hostname, machine ID and
all other settings that could identify the instance
unmodified.</para></listitem>
unmodified.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -265,6 +267,8 @@
<para>With this option no modifications of the container image are retained. Use
<option>--volatile=</option> (described below) for other mechanisms to restrict persistency of
container images during runtime.</para>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
@ -311,7 +315,9 @@
<option>--verity-data=</option> (and optionally <option>--root-hash-sig=</option>) options.</para>
<para>Any other partitions, such as foreign partitions or swap partitions are not mounted. May not be specified
together with <option>--directory=</option>, <option>--template=</option>.</para></listitem>
together with <option>--directory=</option>, <option>--template=</option>.</para>
<xi:include href="version-info.xml" xpointer="v211"/></listitem>
</varlistentry>
<varlistentry>
@ -400,7 +406,9 @@
former are not symlinks into the latter) are not supported by <literal>--volatile=yes</literal> as
container payload. The <option>overlay</option> option does not require any particular preparations
in the OS, but do note that <literal>overlayfs</literal> behaviour differs from regular file systems
in a number of ways, and hence compatibility is limited.</para></listitem>
in a number of ways, and hence compatibility is limited.</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
<varlistentry>
@ -428,6 +436,8 @@
<para>Also see the <varname>RootHash=</varname> option in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
@ -468,7 +478,9 @@
<para>This is for containers which have several bootable directories in them; for example, several
<ulink url="https://ostree.readthedocs.io/en/latest/">OSTree</ulink> deployments. It emulates the
behavior of the boot loader and the initrd which normally select which directory to mount as the root
and start the container's PID 1 in.</para></listitem>
and start the container's PID 1 in.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
</variablelist>
@ -492,6 +504,8 @@
modified to run correctly as PID 1. Or in other words: this switch should be used for pretty much all commands,
except when the command refers to an init or shell implementation, as these are generally capable of running
correctly as PID 1. This option may not be combined with <option>--boot</option>.</para>
<xi:include href="version-info.xml" xpointer="v229"/>
</listitem>
</varlistentry>
@ -546,7 +560,9 @@
<term><option>--chdir=</option></term>
<listitem><para>Change to the specified working directory before invoking the process in the container. Expects
an absolute path in the container's file system namespace.</para></listitem>
an absolute path in the container's file system namespace.</para>
<xi:include href="version-info.xml" xpointer="v229"/></listitem>
</varlistentry>
<varlistentry>
@ -559,7 +575,7 @@
are omitted, the value of the variable with the same name in the program environment will be used.
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -580,7 +596,9 @@
<constant>SIGRTMIN+3</constant> triggers an orderly shutdown). If <option>--boot</option> is not used and this
option is not specified the container's processes are terminated abruptly via <constant>SIGKILL</constant>. For
a list of valid signals, see <citerefentry
project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para></listitem>
project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
@ -593,7 +611,9 @@
With option <option>yes</option> systemd-nspawn waits for the
<literal>READY=1</literal> message from the init process in the container
before sending its own to systemd. For more details about notifications
see <citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para></listitem>
see <citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v231"/></listitem>
</varlistentry>
<varlistentry>
@ -636,7 +656,9 @@
with a random identifier in case <option>--ephemeral</option>
mode is selected. If the root directory selected is the host's
root directory the host's hostname is used as default
instead.</para></listitem>
instead.</para>
<xi:include href="version-info.xml" xpointer="v202"/></listitem>
</varlistentry>
<varlistentry>
@ -652,6 +674,8 @@
exclusively. Note that regardless whether the container's hostname is initialized from the name set with
<option>--hostname=</option> or the one set with <option>--machine=</option>, the container can later override
its kernel hostname freely on its own as well.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@ -678,6 +702,8 @@
<listitem><para>Make the container part of the specified slice, instead of the default
<filename>machine.slice</filename>. This applies only if the machine is run in its own scope unit, i.e. if
<option>--keep-unit</option> isn't used.</para>
<xi:include href="version-info.xml" xpointer="v206"/>
</listitem>
</varlistentry>
@ -688,6 +714,8 @@
machine is run in its own scope unit, i.e. if <option>--keep-unit</option> isn't used. Takes unit property
assignments in the same format as <command>systemctl set-property</command>. This is useful to set memory
limits and similar for the container.</para>
<xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
@ -703,7 +731,9 @@
tools such as <citerefentry
project='man-pages'><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry>. If the container
does not run a service manager, it is recommended to set this option to
<literal>no</literal>.</para></listitem>
<literal>no</literal>.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -719,7 +749,9 @@
<para>Note that passing <option>--keep-unit</option> disables the effect of <option>--slice=</option> and
<option>--property=</option>. Use <option>--keep-unit</option> and <option>--register=no</option> in
combination to disable any kind of unit allocation or registration with
<command>systemd-machined</command>.</para></listitem>
<command>systemd-machined</command>.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
</variablelist>
@ -797,7 +829,9 @@
<para>Note that when user namespacing is used file ownership on disk reflects this, and all of the container's
files and directories are owned by the container's effective user and group IDs. This means that copying files
from and to the container image requires correction of the numeric UID/GID values, according to the UID/GID
shift applied.</para></listitem>
shift applied.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
@ -824,7 +858,7 @@
<option>--private-users=pick</option> is used. This option has no effect if user namespacing is not
used.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@ -841,6 +875,8 @@
<option>-U</option>) on the file system by redoing the operation with the first UID of 0:</para>
<programlisting>systemd-nspawn … --private-users=0 --private-users-ownership=chown</programlisting>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -893,6 +929,8 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<literal>ens1</literal> network interface has shown up. This is required since hardware probing is
fully asynchronous, and network interfaces might be discovered only later during the boot process,
after the container would normally be started without these explicit dependencies.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@ -911,7 +949,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<para>As with <option>--network-interface=</option>, the underlying Ethernet network interface must
already exist at the time the container is started, and thus similar unit file drop-ins as described
above might be useful.</para></listitem>
above might be useful.</para>
<xi:include href="version-info.xml" xpointer="v211"/></listitem>
</varlistentry>
<varlistentry>
@ -931,7 +971,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<para>As with <option>--network-interface=</option>, the underlying Ethernet network interface must
already exist at the time the container is started, and thus similar unit file drop-ins as described
above might be useful.</para></listitem>
above might be useful.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -971,6 +1013,8 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
host-side interface name independently of the container name — but might require a bit more
additional configuration in case bridging in a fashion similar to <option>--network-bridge=</option>
is desired.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@ -986,7 +1030,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
used multiple times, and allows configuration of the network
interface names. Note that <option>--network-bridge=</option>
has no effect on interfaces created with
<option>--network-veth-extra=</option>.</para></listitem>
<option>--network-veth-extra=</option>.</para>
<xi:include href="version-info.xml" xpointer="v228"/></listitem>
</varlistentry>
<varlistentry>
@ -1002,7 +1048,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<para>As with <option>--network-interface=</option>, the underlying bridge network interface must
already exist at the time the container is started, and thus similar unit file drop-ins as described
above might be useful.</para></listitem>
above might be useful.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -1031,6 +1079,8 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
network interfaces. Using <option>--network-zone=</option> is hence in most cases fully automatic and
sufficient to connect multiple local containers in a joined broadcast domain to the host, with further
connectivity to the external network.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -1048,7 +1098,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
for example, <option>--network-namespace-path=/run/netns/foo</option>.
Note that this option cannot be used together with other
network-related options, such as <option>--private-network</option>
or <option>--network-interface=</option>.</para></listitem>
or <option>--network-interface=</option>.</para>
<xi:include href="version-info.xml" xpointer="v236"/></listitem>
</varlistentry>
<varlistentry>
@ -1067,7 +1119,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
same port as the host port is implied. This option is only
supported if private networking is used, such as with
<option>--network-veth</option>, <option>--network-zone=</option>
<option>--network-bridge=</option>.</para></listitem>
<option>--network-bridge=</option>.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
</variablelist>
@ -1102,7 +1156,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<para>This option sets the bounding set of capabilities which
also limits the ambient capabilities as given with the
<option>--ambient-capability=</option>.</para></listitem>
<option>--ambient-capability=</option>.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -1118,7 +1174,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<para>This option sets the bounding set of capabilities which
also limits the ambient capabilities as given with the
<option>--ambient-capability=</option>.</para></listitem>
<option>--ambient-capability=</option>.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -1152,7 +1210,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
on the payload code of the container cannot acquire new privileges, i.e. the "setuid" file bit as
well as file system capabilities will not have an effect anymore. See <citerefentry
project='man-pages'><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry> for
details about this flag. </para></listitem>
details about this flag. </para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -1168,7 +1228,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
system call allow list (as opposed to a deny list!), and this command line option hence adds or
removes entries from the default allow list, depending on the <literal>~</literal> prefix. Note that
the applied system call filter is also altered implicitly if additional capabilities are passed using
the <command>--capabilities=</command>.</para></listitem>
the <command>--capabilities=</command>.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -1177,6 +1239,8 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<listitem><para>Sets the SELinux security context to be used
to label processes in the container.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@ -1187,6 +1251,8 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<listitem><para>Sets the SELinux security context to be used
to label files in the virtual API file systems in the
container.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
</variablelist>
@ -1218,7 +1284,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
(i.e. <option>--private-users=</option> is used, see above), any limits set will be applied to the resource
usage of the same user on all local containers as well as the host. This means particular care needs to be
taken with these limits as they might be triggered by possibly less trusted code. Example:
<literal>--rlimit=RLIMIT_NOFILE=8192:16384</literal>.</para></listitem>
<literal>--rlimit=RLIMIT_NOFILE=8192:16384</literal>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -1228,7 +1296,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<filename>/proc/self/oom_score_adj</filename> which influences the preference with which this container is
terminated when memory becomes scarce. For details see <citerefentry
project='man-pages'><refentrytitle>proc</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Takes an
integer in the range -1000…1000.</para></listitem>
integer in the range -1000…1000.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -1237,7 +1307,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<listitem><para>Controls the CPU affinity of the container payload. Takes a comma separated list of CPU numbers
or number ranges (the latter's start and end value separated by dashes). See <citerefentry
project='man-pages'><refentrytitle>sched_setaffinity</refentrytitle><manvolnum>2</manvolnum></citerefentry> for
details.</para></listitem>
details.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -1250,7 +1322,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<literal>x86-64</literal> are supported. This is useful when
running a 32-bit container on a 64-bit host. If this setting
is not used, the personality reported in the container is the
same as the one reported on the host.</para></listitem>
same as the one reported on the host.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
</variablelist>
@ -1314,7 +1388,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
bind mount anyway). Note that both if the file is bind mounted and if it is copied no further
propagation of configuration is generally done after the one-time early initialization (this is
because the file is usually updated through copying and renaming). Defaults to
<literal>auto</literal>.</para></listitem>
<literal>auto</literal>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -1334,7 +1410,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<literal>auto</literal> and the <filename>/etc/localtime</filename> file of the host is a symlink,
then <literal>symlink</literal> mode is used, and <literal>copy</literal> otherwise, except if the
image is read-only in which case <literal>bind</literal> is used instead. Defaults to
<literal>auto</literal>.</para></listitem>
<literal>auto</literal>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -1368,14 +1446,18 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<literal>auto</literal> is used.</para>
<para>Note that <option>--link-journal=try-guest</option> is the default if the
<filename>systemd-nspawn@.service</filename> template unit file is used.</para></listitem>
<filename>systemd-nspawn@.service</filename> template unit file is used.</para>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
<varlistentry>
<term><option>-j</option></term>
<listitem><para>Equivalent to
<option>--link-journal=try-guest</option>.</para></listitem>
<option>--link-journal=try-guest</option>.</para>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
</variablelist>
@ -1435,7 +1517,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
directories continue to be owned by the relevant host users and groups, which do not exist in the container,
and thus show up under the wildcard UID 65534 (nobody). If such bind mounts are created, it is recommended to
make them read-only, using <option>--bind-ro=</option>. Alternatively you can use the "idmap" mount option to
map the filesystem IDs.</para></listitem>
map the filesystem IDs.</para>
<xi:include href="version-info.xml" xpointer="v198"/></listitem>
</varlistentry>
<varlistentry>
@ -1516,7 +1600,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<para>Note that this option cannot be used to replace the root file system of the container with a temporary
file system. However, the <option>--volatile=</option> option described below provides similar
functionality, with a focus on implementing stateless operating system images.</para></listitem>
functionality, with a focus on implementing stateless operating system images.</para>
<xi:include href="version-info.xml" xpointer="v214"/></listitem>
</varlistentry>
<varlistentry>
@ -1566,7 +1652,9 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<para>Note that this option cannot be used to replace the root file system of the container with an overlay
file system. However, the <option>--volatile=</option> option described above provides similar functionality,
with a focus on implementing stateless operating system images.</para></listitem>
with a focus on implementing stateless operating system images.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
</variablelist>
</refsect2>

10
man/systemd-run.xml
View File

@ -131,7 +131,9 @@
<term><option>-u</option></term>
<listitem><para>Use this unit name instead of an automatically
generated one.</para></listitem>
generated one.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@ -220,6 +222,8 @@
<varname>RemainAfterExit=</varname> in
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v207"/>
</listitem>
</varlistentry>
@ -306,7 +310,7 @@
<para>Also see <varname>Environment=</varname> in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -432,6 +436,8 @@
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
<command>set-property</command> command. These options may not be combined with
<option>--scope</option> or <option>--pty</option>.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>

6
man/systemd-socket-activate.xml
View File

@ -132,7 +132,7 @@
ignored. In case less names are given than descriptors, the remaining file descriptors will be unnamed.
</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="help" />
@ -162,7 +162,9 @@
<term><varname>$SYSTEMD_LOG_LOCATION</varname></term>
<listitem><para>Same as in
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para></listitem>
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
</variablelist>
</refsect1>

2
man/systemd-suspend.service.xml
View File

@ -108,6 +108,8 @@
<listitem><para>Suspend, hibernate, suspend then hibernate, or put the
system to hybrid sleep.</para>
<xi:include href="version-info.xml" xpointer="v203"/>
</listitem>
</varlistentry>
</variablelist>

18
man/systemd-system.conf.xml
View File

@ -81,7 +81,9 @@
<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>
details.</para>
<xi:include href="version-info.xml" xpointer="v198"/></listitem>
</varlistentry>
<varlistentry>
@ -182,7 +184,9 @@
recommended to enable <varname>KExecWatchdogSec=</varname> only if
<varname>RuntimeWatchdogSec=</varname> is also enabled.</para>
<para>These settings have no effect if a hardware watchdog is not available.</para></listitem>
<para>These settings have no effect if a hardware watchdog is not available.</para>
<xi:include href="version-info.xml" xpointer="v198"/></listitem>
</varlistentry>
<varlistentry>
@ -388,7 +392,9 @@
default to &DEFAULT_TIMEOUT; in the system manager and &DEFAULT_USER_TIMEOUT; in the user manager.
<varname>DefaultTimeoutAbortSec=</varname> is not set by default so that all units fall back to
<varname>TimeoutStopSec=</varname>. <varname>DefaultRestartSec=</varname> defaults to 100 ms.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -417,7 +423,9 @@
for details on the per-service settings.
<varname>DefaultStartLimitIntervalSec=</varname> defaults to
10s. <varname>DefaultStartLimitBurst=</varname> defaults to
5.</para></listitem>
5.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -482,6 +490,8 @@
<varname>DefaultMemoryAccounting=</varname> defaults to &MEMORY_ACCOUNTING_DEFAULT;.
<varname>DefaultTasksAccounting=</varname> defaults to yes.
The other settings default to no.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>

2
man/systemd-timesyncd.service.xml
View File

@ -87,7 +87,7 @@
ensure that the system clock remains somewhat reasonably initialized and roughly monotonic across
reboots, in case no battery-buffered local RTC is available.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>

2
man/systemd-tmpfiles.xml
View File

@ -180,7 +180,7 @@
specified prefix. This option can be specified multiple
times.</para>
<xi:include href="version-info.xml" xpointer="v212"/></listitem>
<xi:include href="version-info.xml" xpointer="v207"/></listitem>
</varlistentry>
<varlistentry>

2
man/systemd-tty-ask-password-agent.xml
View File

@ -108,7 +108,7 @@
the calling TTY. If <replaceable>DEVICE</replaceable> is not specified,
<filename>/dev/console</filename> will be used.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="help" />

18
man/systemd-udevd.service.xml
View File

@ -65,6 +65,8 @@
<term><option>--daemon</option></term>
<listitem>
<para>Detach and run in the background.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -73,6 +75,8 @@
<term><option>--debug</option></term>
<listitem>
<para>Print debug messages to standard error.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -81,6 +85,8 @@
<term><option>--children-max=</option></term>
<listitem>
<para>Limit the number of events executed in parallel.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -93,6 +99,8 @@
might be useful when debugging system crashes during
coldplug caused by loading non-working kernel
modules.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -102,6 +110,8 @@
<listitem>
<para>Set the number of seconds to wait for events to finish. After
this time, the event will be terminated. The default is 180 seconds.</para>
<xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
@ -132,6 +142,8 @@
<option>late</option>, names will be resolved for every event.
When set to <option>never</option>, names will never be resolved
and all devices will be owned by root.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@ -159,7 +171,7 @@
<listitem>
<para>Limit the number of events executed in parallel.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
<varlistentry>
@ -171,7 +183,7 @@
debugging system crashes during coldplug caused by loading
non-working kernel modules.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
<varlistentry>
@ -182,7 +194,7 @@
of seconds. This option might be useful if events are
terminated due to kernel drivers taking too long to initialize.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
<xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
<varlistentry>

212
man/systemd.exec.xml
View File

@ -190,7 +190,9 @@
<citerefentry><refentrytitle>systemd-soft-reboot.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>),
in case the service is configured to survive it.</para>
<xi:include href="system-only.xml" xpointer="singular"/></listitem>
<xi:include href="system-only.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@ -350,7 +352,9 @@
<para>In order to allow propagating mounts at runtime in a safe manner, <filename>/run/systemd/propagate</filename>
on the host will be used to set up new mounts, and <filename>/run/host/incoming/</filename> in the private namespace
will be used as an intermediate step to store them before being moved to the final mount point.</para></listitem>
will be used as an intermediate step to store them before being moved to the final mount point.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@ -440,7 +444,9 @@
<varname>InaccessiblePaths=</varname>, or under <filename>/home/</filename> and other protected
directories if <varname>ProtectHome=yes</varname> is
specified. <varname>TemporaryFileSystem=</varname> with <literal>:ro</literal> or
<varname>ProtectHome=tmpfs</varname> should be used instead.</para></listitem>
<varname>ProtectHome=tmpfs</varname> should be used instead.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@ -674,7 +680,9 @@
owned by the dynamic user/group that are not subject to the lifecycle and access guarantees of the
service. Note that this option is currently incompatible with D-Bus policies, thus a service using
this option may currently not allocate a D-Bus service name (note that this does not affect calling
into other D-Bus services). Defaults to off.</para></listitem>
into other D-Bus services). Defaults to off.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -779,7 +787,9 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
give it some capabilities. Note that in this case option <constant>keep-caps</constant> is automatically added
to <varname>SecureBits=</varname> to retain the capabilities over the user
change. <varname>AmbientCapabilities=</varname> does not affect commands prefixed with
<literal>+</literal>.</para></listitem>
<literal>+</literal>.</para>
<xi:include href="version-info.xml" xpointer="v229"/></listitem>
</varlistentry>
</variablelist>
@ -819,7 +829,9 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<citerefentry
project='man-pages'><refentrytitle>crontab</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd-run</refentrytitle><manvolnum>1</manvolnum></citerefentry>, or
arbitrary IPC services.</para></listitem>
arbitrary IPC services.</para>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
<varlistentry>
@ -856,7 +868,9 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
non-overridden context. This does not affect commands prefixed with <literal>+</literal>. See
<citerefentry
project='die-net'><refentrytitle>setexeccon</refentrytitle><manvolnum>3</manvolnum></citerefentry>
for details.</para></listitem>
for details.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -866,6 +880,8 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
this profile when started. Profiles must already be loaded in the kernel, or the unit will fail. If
prefixed by <literal>-</literal>, all errors will be ignored. This setting has no effect if AppArmor
is not enabled. This setting does not affect commands prefixed with <literal>+</literal>.</para>
<xi:include href="version-info.xml" xpointer="v210"/>
</listitem>
</varlistentry>
@ -881,7 +897,9 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<para>The value may be prefixed by <literal>-</literal>, in which case all errors will be ignored. An empty
value may be specified to unset previous assignments. This does not affect commands prefixed with
<literal>+</literal>.</para></listitem>
<literal>+</literal>.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
</variablelist>
@ -1146,7 +1164,9 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<option>inherit</option> is selected the unique invocation ID for the unit (see below) is added as a protected
key by the name <literal>invocation_id</literal> to the newly created session keyring. Defaults to
<option>private</option> for services of the system service manager and to <option>inherit</option> for
non-service units and for services of the user service manager.</para></listitem>
non-service units and for services of the user service manager.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -1191,7 +1211,9 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
feature 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. This
option is not useful on architectures for which only one native word width was ever available, such
as <constant>m68k</constant> (32-bit only) or <constant>alpha</constant> (64-bit only).</para></listitem>
as <constant>m68k</constant> (32-bit only) or <constant>alpha</constant> (64-bit only).</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -1360,7 +1382,9 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<varname>ReadWritePaths=</varname> may be used to exclude specific directories from being made read-only. This
setting is implied if <varname>DynamicUser=</varname> is set. This setting cannot ensure protection in all
cases. In general it has the same limitations as <varname>ReadOnlyPaths=</varname>, see below. Defaults to
off.</para></listitem>
off.</para>
<xi:include href="version-info.xml" xpointer="v214"/></listitem>
</varlistentry>
<varlistentry>
@ -1387,7 +1411,9 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<varname>DynamicUser=</varname> is set. This setting cannot ensure protection in all cases. In
general it has the same limitations as <varname>ReadOnlyPaths=</varname>, see below.</para>
<xi:include href="system-or-user-ns.xml" xpointer="singular"/></listitem>
<xi:include href="system-or-user-ns.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v214"/></listitem>
</varlistentry>
<varlistentry>
@ -1529,7 +1555,9 @@ StateDirectory=aaa/bbb ccc</programlisting>
<programlisting>RuntimeDirectory=foo:bar foo:baz</programlisting>
the service manager creates <filename index='false'>/run/foo</filename> (if it does not exist), and
<filename index='false'>/run/bar</filename> plus <filename index='false'>/run/baz</filename> as symlinks to
<filename index='false'>/run/foo</filename>.</para></listitem>
<filename index='false'>/run/foo</filename>.</para>
<xi:include href="version-info.xml" xpointer="v211"/></listitem>
</varlistentry>
<varlistentry>
@ -1544,7 +1572,9 @@ StateDirectory=aaa/bbb ccc</programlisting>
<varname>ConfigurationDirectory=</varname>, respectively, as an octal number. Defaults to
<constant>0755</constant>. See "Permissions" in <citerefentry
project='man-pages'><refentrytitle>path_resolution</refentrytitle><manvolnum>7</manvolnum></citerefentry> for a
discussion of the meaning of permission bits.</para></listitem>
discussion of the meaning of permission bits.</para>
<xi:include href="version-info.xml" xpointer="v234"/></listitem>
</varlistentry>
<varlistentry>
@ -1558,7 +1588,9 @@ StateDirectory=aaa/bbb ccc</programlisting>
foo.service</command>. If set to <option>yes</option>, then the directories are not removed when the service is
stopped. Note that since the runtime directory <filename>/run/</filename> is a mount point of
<literal>tmpfs</literal>, then for system services the directories specified in
<varname>RuntimeDirectory=</varname> are removed when the system is rebooted.</para></listitem>
<varname>RuntimeDirectory=</varname> are removed when the system is rebooted.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -1643,7 +1675,9 @@ NoExecPaths=/
ExecPaths=/usr/sbin/my_daemon /usr/lib /usr/lib64
</programlisting></para>
<xi:include href="system-or-user-ns.xml" xpointer="plural"/></listitem>
<xi:include href="system-or-user-ns.xml" xpointer="plural"/>
<xi:include href="version-info.xml" xpointer="v231"/></listitem>
</varlistentry>
<varlistentry>
@ -1737,7 +1771,9 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
<para>When access to some but not all devices must be possible, the <varname>DeviceAllow=</varname>
setting might be used instead. See
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -1897,7 +1933,9 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
<para>Note that the implementation of this setting might be impossible (for example if user namespaces are not
available), and the unit should be written in a way that does not solely rely on this setting for
security.</para></listitem>
security.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -1968,7 +2006,9 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
inaccessible. If <varname>ProtectKernelTunables=</varname> is set,
<varname>MountAPIVFS=yes</varname> is implied.</para>
<xi:include href="system-or-user-ns.xml" xpointer="singular"/></listitem>
<xi:include href="system-or-user-ns.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -1989,7 +2029,9 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
but the unit doesn't have the <constant>CAP_SYS_ADMIN</constant> capability (e.g. services for
which <varname>User=</varname> is set), <varname>NoNewPrivileges=yes</varname> is implied.</para>
<xi:include href="system-or-user-ns.xml" xpointer="singular"/></listitem>
<xi:include href="system-or-user-ns.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -2025,7 +2067,9 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
above. Defaults to off. If <varname>ProtectControlGroups=</varname> is set, <varname>MountAPIVFS=yes</varname>
is implied.</para>
<xi:include href="system-only.xml" xpointer="singular"/></listitem>
<xi:include href="system-only.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -2060,7 +2104,9 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
<constant>AF_UNIX</constant> address family should be included in the configured allow list as it is frequently
used for local communication, including for
<citerefentry><refentrytitle>syslog</refentrytitle><manvolnum>2</manvolnum></citerefentry>
logging.</para></listitem>
logging.</para>
<xi:include href="version-info.xml" xpointer="v211"/></listitem>
</varlistentry>
<varlistentry>
@ -2195,7 +2241,9 @@ RestrictNamespaces=cgroup net</programlisting>
If the second line is prefixed with <literal>~</literal>, e.g.,
<programlisting>RestrictNamespaces=cgroup ipc
RestrictNamespaces=~cgroup net</programlisting>
then, only <constant>ipc</constant> is set.</para></listitem>
then, only <constant>ipc</constant> is set.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@ -2207,7 +2255,9 @@ RestrictNamespaces=~cgroup net</programlisting>
<varname>Personality=</varname> directive. This may be useful to improve security, because odd personality
emulations may be poorly tested and source of vulnerabilities. If running in user mode, or in system mode, but
without the <constant>CAP_SYS_ADMIN</constant> capability (e.g. setting <varname>User=</varname>),
<varname>NoNewPrivileges=yes</varname> is implied.</para></listitem>
<varname>NoNewPrivileges=yes</varname> is implied.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -2239,7 +2289,9 @@ RestrictNamespaces=~cgroup net</programlisting>
restrictions of this option. Specifically, it is recommended to combine this option with
<varname>SystemCallArchitectures=native</varname> or similar. If running in user mode, or in system
mode, but without the <constant>CAP_SYS_ADMIN</constant> capability (e.g. setting
<varname>User=</varname>), <varname>NoNewPrivileges=yes</varname> is implied.</para></listitem>
<varname>User=</varname>), <varname>NoNewPrivileges=yes</varname> is implied.</para>
<xi:include href="version-info.xml" xpointer="v231"/></listitem>
</varlistentry>
<varlistentry>
@ -2254,7 +2306,9 @@ RestrictNamespaces=~cgroup net</programlisting>
<varname>NoNewPrivileges=yes</varname> is implied. Realtime scheduling policies may be used to monopolize CPU
time for longer periods of time, and may hence be used to lock up or otherwise trigger Denial-of-Service
situations on the system. It is hence recommended to restrict access to realtime scheduling to the few programs
that actually require them. Defaults to off.</para></listitem>
that actually require them. Defaults to off.</para>
<xi:include href="version-info.xml" xpointer="v231"/></listitem>
</varlistentry>
<varlistentry>
@ -2287,7 +2341,9 @@ RestrictNamespaces=~cgroup net</programlisting>
multiple units use the same user or group the IPC objects are removed when the last of these units is
stopped. This setting is implied if <varname>DynamicUser=</varname> is set.</para>
<xi:include href="system-only.xml" xpointer="singular"/></listitem>
<xi:include href="system-only.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -2586,7 +2642,9 @@ SystemCallErrorNumber=EPERM</programlisting>
<varname>PrivateDevices=</varname>, <varname>ProtectSystem=</varname>, <varname>ProtectHome=</varname>,
<varname>ProtectKernelTunables=</varname>, <varname>ProtectControlGroups=</varname>,
<varname>ProtectKernelLogs=</varname>, <varname>ProtectClock=</varname>, <varname>ReadOnlyPaths=</varname>,
<varname>InaccessiblePaths=</varname> and <varname>ReadWritePaths=</varname>.</para></listitem>
<varname>InaccessiblePaths=</varname> and <varname>ReadWritePaths=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
<varlistentry>
@ -2599,7 +2657,9 @@ SystemCallErrorNumber=EPERM</programlisting>
project='man-pages'><refentrytitle>errno</refentrytitle><manvolnum>3</manvolnum></citerefentry> for a
full list of error codes. When this setting is not used, or when the empty string or the special
setting <literal>kill</literal> is assigned, the process will be terminated immediately when the
filter is triggered.</para></listitem>
filter is triggered.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -2631,7 +2691,9 @@ SystemCallErrorNumber=EPERM</programlisting>
<para>System call architectures may also be restricted system-wide via the
<varname>SystemCallArchitectures=</varname> option in the global configuration. See
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
details.</para></listitem>
details.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -2781,7 +2843,9 @@ SystemCallErrorNumber=EPERM</programlisting>
<para>
See <citerefentry
project='man-pages'><refentrytitle>environ</refentrytitle><manvolnum>7</manvolnum></citerefentry> for details
about environment variables.</para></listitem>
about environment variables.</para>
<xi:include href="version-info.xml" xpointer="v228"/></listitem>
</varlistentry>
<varlistentry>
@ -2805,7 +2869,9 @@ SystemCallErrorNumber=EPERM</programlisting>
<para>See "Environment Variables in Spawned Processes" below for a description of how those
settings combine to form the inherited environment. See <citerefentry
project='man-pages'><refentrytitle>environ</refentrytitle><manvolnum>7</manvolnum></citerefentry> for general
information about environment variables.</para></listitem>
information about environment variables.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
</variablelist>
@ -3392,7 +3458,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
consumers.</para>
<para>For further information see <ulink url="https://systemd.io/CREDENTIALS">System and Service
Credentials</ulink> documentation.</para></listitem>
Credentials</ulink> documentation.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
</varlistentry>
<varlistentry>
@ -3449,7 +3517,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<varname>SetCredential=</varname>. As such, <varname>SetCredential=</varname> will act as default if
no credentials are found by any of the former. In this case not being able to retrieve the credential
from the path specified in <varname>LoadCredential=</varname> or
<varname>LoadCredentialEncrypted=</varname> is not considered fatal.</para></listitem>
<varname>LoadCredentialEncrypted=</varname> is not considered fatal.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@ -3489,7 +3559,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
utmp/wtmp logic. If <literal>user</literal> is set, first an <constant>INIT_PROCESS</constant> entry, then a
<constant>LOGIN_PROCESS</constant> entry and finally a <constant>USER_PROCESS</constant> entry is
generated. In this case, the invoked process may be any process that is suitable to be run as session
leader. Defaults to <literal>init</literal>.</para></listitem>
leader. Defaults to <literal>init</literal>.</para>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
</varlistentry>
</variablelist>
@ -3562,7 +3634,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<literal><filename>/usr/local/sbin</filename>:<filename>/usr/local/bin</filename>:<filename>/usr/sbin</filename>:<filename>/usr/bin</filename></literal>
in the system manager. In case of the user manager, a different path may be configured by the
distribution. It is recommended to not rely on the order of entries, and have only one program
with a given name in <varname>$PATH</varname>.</para></listitem>
with a given name in <varname>$PATH</varname>.</para>
<xi:include href="version-info.xml" xpointer="v208"/></listitem>
</varlistentry>
<varlistentry>
@ -3573,7 +3647,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
or on the kernel command line (see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> and
<citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry>).
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v208"/></listitem>
</varlistentry>
<varlistentry>
@ -3587,7 +3663,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<varname>User=</varname> set, which includes user
<command>systemd</command> instances. See
<citerefentry project='die-net'><refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v208"/></listitem>
</varlistentry>
<varlistentry>
@ -3597,7 +3675,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
as 32 character hexadecimal string. A new ID is assigned each time the unit changes from an inactive state into
an activating or active state, and may be used to identify this specific runtime cycle, in particular in data
stored offline, such as the journal. The same ID is passed to all processes run as part of the
unit.</para></listitem>
unit.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -3607,7 +3687,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
services run by the user <command>systemd</command> instance, as well as any system services that use
<varname>PAMName=</varname> with a PAM stack that includes <command>pam_systemd</command>. See below and
<citerefentry><refentrytitle>pam_systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry> for more
information.</para></listitem>
information.</para>
<xi:include href="version-info.xml" xpointer="v208"/></listitem>
</varlistentry>
<varlistentry>
@ -3621,6 +3703,8 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<varname>RuntimeDirectory=</varname>, <varname>StateDirectory=</varname>,
<varname>CacheDirectory=</varname>, <varname>LogsDirectory=</varname>, and
<varname>ConfigurationDirectory=</varname> when those settings are used.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
@ -3631,7 +3715,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<varname>ImportCredential=</varname>/<varname>LoadCredential=</varname>/<varname>SetCredential=</varname>.
The directory is marked read-only and is placed in unswappable memory (if supported and permitted),
and is only accessible to the UID associated with the unit via <varname>User=</varname> or
<varname>DynamicUser=</varname> (and the superuser).</para></listitem>
<varname>DynamicUser=</varname> (and the superuser).</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
</varlistentry>
<varlistentry>
@ -3639,14 +3725,18 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<listitem><para>The PID of the unit's main process if it is
known. This is only set for control processes as invoked by
<varname>ExecReload=</varname> and similar.</para></listitem>
<varname>ExecReload=</varname> and similar.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>$MANAGERPID</varname></term>
<listitem><para>The PID of the user <command>systemd</command>
instance, set for processes spawned by it.</para></listitem>
instance, set for processes spawned by it.</para>
<xi:include href="version-info.xml" xpointer="v208"/></listitem>
</varlistentry>
<varlistentry>
@ -3657,7 +3747,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<listitem><para>Information about file descriptors passed to a
service for socket activation. See
<citerefentry><refentrytitle>sd_listen_fds</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v208"/></listitem>
</varlistentry>
<varlistentry>
@ -3665,7 +3757,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<listitem><para>The socket <function>sd_notify()</function> talks to. See
<citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v229"/></listitem>
</varlistentry>
<varlistentry>
@ -3674,7 +3768,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<listitem><para>Information about watchdog keep-alive notifications. See
<citerefentry><refentrytitle>sd_watchdog_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v229"/></listitem>
</varlistentry>
<varlistentry>
@ -3698,14 +3794,18 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<varname>StandardOutput=tty</varname>, or
<varname>StandardError=tty</varname>). See
<citerefentry project='man-pages'><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>$LOG_NAMESPACE</varname></term>
<listitem><para>Contains the name of the selected logging namespace when the
<varname>LogNamespace=</varname> service setting is used.</para></listitem>
<varname>LogNamespace=</varname> service setting is used.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@ -3731,7 +3831,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
protocol to the native journal protocol (using
<citerefentry><refentrytitle>sd_journal_print</refentrytitle><manvolnum>3</manvolnum></citerefentry> and other
functions) if their standard output or standard error output is connected to the journal anyway, thus enabling
delivery of structured metadata along with logged messages.</para></listitem>
delivery of structured metadata along with logged messages.</para>
<xi:include href="version-info.xml" xpointer="v231"/></listitem>
</varlistentry>
<varlistentry>
@ -3798,7 +3900,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
though this variable is available in both <varname>ExecStop=</varname> and <varname>ExecStopPost=</varname>, it
is usually a better choice to place monitoring tools in the latter, as the former is only invoked for services
that managed to start up correctly, and the latter covers both services that failed during their start-up and
those which failed during their runtime.</para></listitem>
those which failed during their runtime.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -3914,7 +4018,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
</row>
</tbody>
</tgroup>
</table></listitem>
</table>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@ -3952,7 +4058,9 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details. Service code may use this environment variable to automatically generate a PID file at
the location configured in the unit file. This field is set to an absolute path in the file
system.</para></listitem>
system.</para>
<xi:include href="version-info.xml" xpointer="v242"/></listitem>
</varlistentry>
<varlistentry>

2
man/systemd.journal-fields.xml
View File

@ -531,6 +531,8 @@
system and session units. See
<citerefentry><refentrytitle>coredumpctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
</variablelist>

58
man/systemd.link.xml
View File

@ -146,6 +146,8 @@
(for IPv6 tunnel), or 20 (for InfiniBand). This option may appear more than once, in which
case the lists are merged. If the empty string is assigned to this option, the list of
hardware addresses defined prior to this is reset. Defaults to unset.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -170,6 +172,8 @@
<para>A whitespace-separated list of shell-style globs matching
the persistent path, as exposed by the udev property
<varname>ID_PATH</varname>.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -180,6 +184,8 @@
device, as exposed by the udev property <varname>ID_NET_DRIVER</varname> of its parent device, or
if that is not set, the driver as exposed by <command>ethtool -i</command> of the device itself.
If the list is prefixed with a "!", the test is inverted.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -192,6 +198,8 @@
Valid types are named either from the udev <literal>DEVTYPE</literal> attribute, or
<literal>ARPHRD_</literal> macros in <filename>linux/if_arp.h</filename>, so this is not comprehensive.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -249,6 +257,8 @@
for details. When prefixed with an exclamation mark (<literal>!</literal>), the result is negated.
If an empty string is assigned, the previously assigned value is cleared.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -261,6 +271,8 @@
for details. When prefixed with an exclamation mark (<literal>!</literal>), the result is negated.
If an empty string is assigned, the previously assigned value is cleared.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -273,6 +285,8 @@
for details. When prefixed with an exclamation mark (<literal>!</literal>), the result is negated.
If an empty string is assigned, the previously assigned value is cleared.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -313,6 +327,8 @@
for details. When prefixed with an exclamation mark (<literal>!</literal>), the result is negated.
If an empty string is assigned, the previously assigned value is cleared.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -344,12 +360,16 @@
<term><varname>Description=</varname></term>
<listitem>
<para>A description of the device.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>Alias=</varname></term>
<listitem>
<para>The <varname>ifalias</varname> interface property is set to this value.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -372,6 +392,8 @@
properties to exist for the link. On hardware where these
properties are not set, the generation of a persistent MAC address
will fail.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -383,6 +405,8 @@
boot. Either way, the random address will have the
<literal>unicast</literal> and
<literal>locally administered</literal> bits set.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -397,6 +421,8 @@
</variablelist>
<para>An empty string assignment is equivalent to setting <literal>none</literal>.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -406,7 +432,7 @@
<varname>MACAddressPolicy=</varname> must either be unset, empty, or <literal>none</literal>.
</para>
<xi:include href="version-info.xml" xpointer="v215"/>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -439,6 +465,8 @@
Hardware Database with the key
<varname>ID_NET_NAME_FROM_DATABASE</varname>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -449,6 +477,8 @@
udev property <varname>ID_NET_NAME_ONBOARD</varname>.
See <citerefentry><refentrytitle>systemd.net-naming-scheme</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -459,6 +489,8 @@
udev property <varname>ID_NET_NAME_SLOT</varname>.
See <citerefentry><refentrytitle>systemd.net-naming-scheme</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -469,6 +501,8 @@
<varname>ID_NET_NAME_PATH</varname>.
See <citerefentry><refentrytitle>systemd.net-naming-scheme</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -479,6 +513,8 @@
<varname>ID_NET_NAME_MAC</varname>.
See <citerefentry><refentrytitle>systemd.net-naming-scheme</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -491,6 +527,8 @@
</listitem>
</varlistentry>
</variablelist>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -517,6 +555,8 @@
ambiguity with interface specification by numeric indexes), as are the special strings
<literal>.</literal>, <literal>..</literal>, <literal>all</literal> and
<literal>default</literal>.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -582,6 +622,8 @@
<para>The maximum transmission unit in bytes to set for the
device. The usual suffixes K, M, G are supported and are
understood to the base of 1024.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -590,6 +632,8 @@
<para>The speed to set for the device, the value is rounded
down to the nearest Mbps. The usual suffixes K, M, G are
supported and are understood to the base of 1000.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -597,6 +641,8 @@
<listitem>
<para>The duplex mode to set for the device. The accepted values are <option>half</option> and
<option>full</option>.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -626,6 +672,8 @@
<term><option>phy</option></term>
<listitem>
<para>Wake on PHY activity.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -665,6 +713,8 @@
<listitem>
<para>Wake on receipt of a magic packet.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -690,6 +740,8 @@
<para>Defaults to unset, and the device's default will be used. This setting can be specified
multiple times. If an empty string is assigned, then the all previous assignments are
cleared.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -917,6 +969,8 @@
Takes an unsigned integer in the range 1…4294967295 or <literal>max</literal>. If set to
<literal>max</literal>, the advertised maximum value of the hardware will be used. When
unset, the number will not be changed. Defaults to unset.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
<varlistentry>
@ -930,6 +984,8 @@
the range 1…4294967295 or <literal>max</literal>. If set to <literal>max</literal>, the
advertised maximum value of the hardware will be used. When unset, the number will not be
changed. Defaults to unset.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<varlistentry>

14
man/systemd.mount.xml
View File

@ -289,7 +289,9 @@
<listitem><para>An automount unit will be created for the file
system. See
<citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details.</para></listitem>
for details.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -317,6 +319,8 @@
<filename>/etc/fstab</filename>, and will be
ignored when part of the <varname>Options=</varname>
setting in a unit file.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -443,6 +447,8 @@
<para>Note that if <option>x-systemd.automount</option> (see above) is used, neither
<option>auto</option> nor <option>noauto</option> have any effect. The matching automount unit will
be added as a dependency to the appropriate target.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -453,6 +459,8 @@
<filename>local-fs.target</filename> or <filename>remote-fs.target</filename>. Moreover the mount unit is not
ordered before these target units. This means that the boot will continue without waiting for the mount unit
and regardless whether the mount point can be mounted successfully.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -466,7 +474,9 @@
leave the partition mounted until final shutdown. Or in other words, if this flag is set it is
assumed the mount shall be active during the entire regular runtime of the system, i.e. established
before the initrd transitions into the host all the way until the host transitions to the final
shutdown phase.</para></listitem>
shutdown phase.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>

6
man/systemd.net-naming-scheme.xml
View File

@ -129,6 +129,8 @@
</tbody>
</tgroup>
</table>
<xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
@ -243,6 +245,8 @@
<para>In some configurations a parent PCI bridge of a given network controller may be associated
with a slot. In such case we don't generate this device property to avoid possible naming conflicts.</para>
<xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
@ -311,6 +315,8 @@
<para>For PCI, BCMA, and USB devices, the same rules as described above for slot naming are
used.</para>
<xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
</variablelist>

18
man/systemd.netdev.xml
View File

@ -243,6 +243,8 @@
<listitem>
<para>The interface name used when creating the netdev.
This setting is compulsory.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -251,6 +253,8 @@
<para>The netdev kind. This setting is compulsory. See the
<literal>Supported netdev kinds</literal> section for the
valid keys.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -452,6 +456,8 @@
<listitem>
<para>The VLAN ID to use. An integer in the range 0…4094.
This setting is compulsory.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -515,6 +521,8 @@
1…4294967294, in the format <literal>from</literal>-<literal>to</literal>, e.g.,
<literal>21-7 45-5</literal>. Note that <literal>from</literal> must be greater than or equal
to <literal>to</literal>. When unset, the kernel's default will be used.</para>
<xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
</variablelist>
@ -538,6 +546,8 @@
<literal>passthru</literal>, and
<literal>source</literal>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<varlistentry>
@ -742,7 +752,7 @@
<listitem>
<para>Takes a boolean. When true, transmitting UDP checksums when doing VXLAN/IPv4 is turned on.</para>
<xi:include href="version-info.xml" xpointer="v232"/>
<xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
<varlistentry>
@ -758,7 +768,7 @@
<listitem>
<para>Takes a boolean. When true, receiving zero checksums in VXLAN/IPv6 is turned on.</para>
<xi:include href="version-info.xml" xpointer="v232"/>
<xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
<varlistentry>
@ -846,6 +856,8 @@
<para>Takes a boolean. When true, the vxlan interface is created without any underlying network
interface. Defaults to false, which means that a .network file that requests this VXLAN interface
using <varname>VXLAN=</varname> is required for the VXLAN to be created.</para>
<xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
</variablelist>
@ -864,6 +876,8 @@
<listitem>
<para>Specifies the Virtual Network Identifier (VNI) to use, a number between 0 and 16777215. This
field is mandatory.</para>
<xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
<varlistentry>

144
man/systemd.network.xml
View File

@ -98,6 +98,8 @@
<para>A whitespace-separated list of shell-style globs matching the device name, as exposed
by the udev property <literal>INTERFACE</literal>, or device's alternative names. If the
list is prefixed with a "!", the test is inverted.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -157,6 +159,8 @@
<term><varname>MACAddress=</varname></term>
<listitem>
<para>The hardware address to set for the device.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@ -344,6 +348,8 @@
<term><varname>Description=</varname></term>
<listitem>
<para>A description of the device. This is only used for presentation purposes.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -365,6 +371,8 @@
<para>See the [DHCPv4] or [DHCPv6] sections below for further configuration options for the
DHCP client support.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -645,6 +653,8 @@ Table=1234</programlisting></para>
10.0.0.0/8 for IPv4, and fd00::/8 for IPv6. This functionality is useful to manage a large
number of dynamically created network interfaces with the same network configuration and
automatic address range assignment.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -655,6 +665,8 @@ Table=1234</programlisting></para>
<citerefentry project='man-pages'><refentrytitle>inet_pton</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
This is a short-hand for a [Route] section only containing a <varname>Gateway=</varname> key.
This option may be specified more than once.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -673,6 +685,8 @@ Table=1234</programlisting></para>
assigned, then the all previous assignments are cleared. This setting is read by
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -996,6 +1010,8 @@ Table=1234</programlisting></para>
to. See
<citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -1015,6 +1031,8 @@ Table=1234</programlisting></para>
VXLAN, or Xfrm to be created on the link. See
<citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
This option may be specified more than once.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -1128,7 +1146,7 @@ Table=1234</programlisting></para>
<para>As in the [Network] section. This setting is mandatory. Each [Address] section can
contain one <varname>Address=</varname> setting.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -1150,6 +1168,8 @@ Table=1234</programlisting></para>
If set to true, then the IPv4 broadcast address will be derived from the
<varname>Address=</varname> setting. If set to false, then the broadcast address will not be
set. Defaults to true, except for wireguard interfaces, where it default to false.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -1158,6 +1178,8 @@ Table=1234</programlisting></para>
<listitem>
<para>Specifies the label for the IPv4 address. The label must be a 7-bit ASCII string with
a length of 1…15 characters. Defaults to unset.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -1197,6 +1219,8 @@ Table=1234</programlisting></para>
address, taking the configured prefix length into account. Takes an unsigned integer in the
range 0…4294967295. When unset or set to 0, the kernel's default value is used. This
setting will be ignored when <varname>AddPrefixRoute=</varname> is false.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
@ -1766,7 +1790,7 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<literal>_ipv6ra</literal>. If <literal>_dhcp4</literal> or <literal>_ipv6ra</literal> is
set, then the gateway address provided by DHCPv4 or IPv6 RA is used.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -1778,7 +1802,7 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
can insert the route in the kernel table without it being complained about. Defaults to
<literal>no</literal>.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
<xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
@ -1787,6 +1811,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<listitem>
<para>The destination prefix of the route. Possibly followed by a slash and the prefix
length. If omitted, a full-length host route is assumed.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -1890,7 +1916,7 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<literal>anycast</literal>, or <literal>nat</literal>, then <literal>local</literal> is used.
In other cases, defaults to <literal>main</literal>.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -1932,6 +1958,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
is generated. If <literal>throw</literal>, route lookup in the current routing table will
fail and the route selection process will return to Routing Policy Database (RPDB). Defaults
to <literal>unicast</literal>.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@ -2078,6 +2106,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
hostname must consist only of 7-bit ASCII lower-case characters and no spaces or dots, and be
formatted as a valid DNS domain name. Otherwise, the hostname is not sent even if this option
is true.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -2087,6 +2117,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>Use this value for the hostname which is sent to the DHCP server, instead of machine's
hostname. Note that the specified hostname must consist only of 7-bit ASCII lower-case
characters and no spaces or dots, and be formatted as a valid DNS domain name.</para>
<xi:include href="version-info.xml" xpointer="v223"/>
</listitem>
</varlistentry>
@ -2117,6 +2149,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
DUID, is used. IAID can be configured by <varname>IAID=</varname>. DUID can be configured by
<varname>DUIDType=</varname> and <varname>DUIDRawData=</varname>. Defaults to
<option>duid</option>.</para>
<xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
@ -2124,6 +2158,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<term><varname>VendorClassIdentifier=</varname></term>
<listitem>
<para>The vendor class identifier used to identify vendor type and configuration.</para>
<xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
@ -2135,6 +2171,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
represents the user class of which the client is a member. Each class sets an identifying
string of information to be used by the DHCP service to classify clients. Takes a
whitespace-separated list of strings.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@ -2144,6 +2182,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>Override the global <varname>DUIDType=</varname> setting for this network. See
<citerefentry><refentrytitle>networkd.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for a description of possible values.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -2153,6 +2193,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>Override the global <varname>DUIDRawData=</varname> setting for this network. See
<citerefentry><refentrytitle>networkd.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for a description of possible values.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -2161,6 +2203,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<listitem>
<para>The DHCP Identity Association Identifier (IAID) for the interface, a 32-bit unsigned
integer.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -2185,6 +2229,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
Windows, in order to reduce the ability to fingerprint and recognize installations. This
means DHCP request sizes will grow and lease data will be more comprehensive than normally,
though most of the requested data is not actually used.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@ -2242,6 +2288,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
sent from the DHCPv4 client. When <literal>CS6</literal> (network control) or
<literal>CS4</literal> (realtime), the corresponding service type will be set. Defaults to
<literal>CS6</literal>.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
@ -2282,6 +2330,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>This corresponds to the <option>nameserver</option> option in
<citerefentry project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -2301,6 +2351,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<listitem>
<para>When true (the default), the NTP servers received from the DHCP server will be used by
<filename>systemd-timesyncd.service</filename>.</para>
<xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
@ -2345,6 +2397,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>Note, some drivers will reset the interfaces if the MTU is changed. For such
interfaces, please try to use <varname>IgnoreCarrierLoss=</varname> with a short timespan,
e.g. <literal>3 seconds</literal>.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -2353,6 +2407,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<listitem>
<para>When true (the default), the hostname received from the DHCP server will be set as the
transient hostname of the system.</para>
<xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
@ -2374,6 +2430,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>When set to true, this setting corresponds to the <option>domain</option> option in
<citerefentry project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
@ -2387,6 +2445,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
own address, the scope will be set to <option>host</option>. Otherwise if the gateway is null
(a direct route), a <option>link</option> scope will be used. For anything else, scope
defaults to <option>global</option>.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@ -2396,6 +2456,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>Set the routing metric for routes specified by the DHCP server (including the prefix
route added for the specified prefix). Takes an unsigned integer in the range 0…4294967295.
Defaults to 1024.</para>
<xi:include href="version-info.xml" xpointer="v217"/>
</listitem>
</varlistentry>
@ -2410,6 +2472,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>When used in combination with <varname>VRF=</varname>, the VRF's routing table is
used when this parameter is not specified.</para>
<xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
@ -2465,7 +2529,9 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<varlistentry>
<term><varname>UseTimezone=</varname></term>
<listitem><para>When true, the timezone received from the DHCP server will be set as timezone
of the local system. Defaults to false.</para></listitem>
of the local system. Defaults to false.</para>
<xi:include href="version-info.xml" xpointer="v226"/></listitem>
</varlistentry>
<varlistentry>
@ -2501,6 +2567,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
This is necessary for devices that cannot receive RAW packets, or that cannot receive packets
at all before an IP address has been configured. On the other hand, this must not be enabled
on networks where broadcasts are filtered out.</para>
<xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
@ -2521,6 +2589,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<term><varname>ListenPort=</varname></term>
<listitem>
<para>Set the port from which the DHCP client packets originate.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
@ -2615,6 +2685,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<term><varname>RequestOptions=</varname></term>
<listitem>
<para>As in the [DHCPv4] section.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
@ -2749,6 +2821,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<term><varname>SendRelease=</varname></term>
<listitem>
<para>As in the [DHCPv4] section.</para>
<xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
@ -2816,6 +2890,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<ulink url="https://tools.ietf.org/html/rfc4291#section-2.5.4">RFC 4291</ulink>, section
2.5.4), in which case the allowed value is hexadecimal, from 0 to 0x7fffffffffffffff
inclusive.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
@ -2826,6 +2902,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
is enabled, the delegated prefixes are distributed through the IPv6 Router Advertisement.
This setting will be ignored when the <varname>DHCPPrefixDelegation=</varname> setting is
enabled on the upstream interface. Defaults to yes.</para>
<xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
@ -2837,6 +2915,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
interface), the EUI-64 algorithm will be used by default to form an interface identifier from
the delegated prefixes. See also <varname>Token=</varname> setting below. Defaults to yes.
</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
@ -2847,6 +2927,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
delegated prefix. This accepts the same syntax as <varname>Token=</varname> in the
[IPv6AcceptRA] section. If <varname>Assign=</varname> is set to false, then this setting will
be ignored. Defaults to unset, which means the EUI-64 algorithm will be used.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
@ -2854,6 +2936,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<term><varname>ManageTemporaryAddress=</varname></term>
<listitem>
<para>As in the [Address] section, but defaults to true.</para>
<xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
@ -2863,6 +2947,8 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
<para>The metric of the route to the delegated prefix subnet. Takes an unsigned integer in
the range 0…4294967295. When set to 0, the kernel's default value is used. Defaults to 256.
</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
@ -3000,6 +3086,8 @@ Token=prefixstable:2002:da8:1::</programlisting></para>
<para>This corresponds to the <option>nameserver</option> option in <citerefentry
project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
@ -3020,6 +3108,8 @@ Token=prefixstable:2002:da8:1::</programlisting></para>
<para>When set to true, this setting corresponds to the <option>domain</option> option in <citerefentry
project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
@ -3409,7 +3499,9 @@ ServerAddress=192.168.0.1/24</programlisting>
<listitem><para>Similar to the <varname>EmitDNS=</varname> and <varname>DNS=</varname> settings
described above, these settings configure whether and what server information for the indicate
protocol shall be emitted as part of the DHCP lease. The same syntax, propagation semantics and
defaults apply as for <varname>EmitDNS=</varname> and <varname>DNS=</varname>.</para></listitem>
defaults apply as for <varname>EmitDNS=</varname> and <varname>DNS=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v226"/></listitem>
</varlistentry>
<varlistentry>
@ -3423,7 +3515,9 @@ ServerAddress=192.168.0.1/24</programlisting>
the router option. When the <varname>EmitRouter=</varname> setting is disabled, the
<varname>Router=</varname> setting will be ignored. The <varname>EmitRouter=</varname> setting
defaults to true, and the <varname>Router=</varname> setting defaults to unset.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@ -3575,7 +3669,9 @@ ServerAddress=192.168.0.1/24</programlisting>
<varlistentry>
<term><varname>MACAddress=</varname></term>
<listitem><para>The hardware address of a device to match. This key is mandatory.</para></listitem>
<listitem><para>The hardware address of a device to match. This key is mandatory.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
<varlistentry>
@ -3609,7 +3705,9 @@ ServerAddress=192.168.0.1/24</programlisting>
<varname>OtherInformation=</varname> is set to
<literal>true</literal>. Both settings default to
<literal>false</literal>, which means that a DHCPv6 server is not being
used.</para></listitem>
used.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -3618,6 +3716,8 @@ ServerAddress=192.168.0.1/24</programlisting>
<listitem><para>Takes a timespan. Configures the IPv6 router lifetime in seconds. The value must be 0
seconds, or between 4 seconds and 9000 seconds. When set to 0, the host is not acting as a router.
Defaults to 1800 seconds (30 minutes).</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@ -3642,7 +3742,9 @@ ServerAddress=192.168.0.1/24</programlisting>
<literal>default</literal> added as synonyms for
<literal>medium</literal> just to make configuration easier. See
<ulink url="https://tools.ietf.org/html/rfc4191">RFC 4191</ulink>
for details. Defaults to <literal>medium</literal>.</para></listitem>
for details. Defaults to <literal>medium</literal>.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -3680,7 +3782,9 @@ ServerAddress=192.168.0.1/24</programlisting>
read from the [Network] section. If the [Network] section does not contain any DNS servers
either, DNS servers from the uplink interface specified in <varname>UplinkInterface=</varname>
will be used. When <varname>EmitDNS=</varname> is false, no DNS server information is sent in
Router Advertisement messages. <varname>EmitDNS=</varname> defaults to true.</para></listitem>
Router Advertisement messages. <varname>EmitDNS=</varname> defaults to true.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -3693,7 +3797,9 @@ ServerAddress=192.168.0.1/24</programlisting>
search domains either, DNS search domains from the uplink interface specified in
<varname>UplinkInterface=</varname> will be used. When <varname>EmitDomains=</varname> is false,
no DNS search domain information is sent in Router Advertisement messages.
<varname>EmitDomains=</varname> defaults to true.</para></listitem>
<varname>EmitDomains=</varname> defaults to true.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -3701,7 +3807,9 @@ ServerAddress=192.168.0.1/24</programlisting>
<listitem><para>Lifetime in seconds for the DNS server addresses listed in
<varname>DNS=</varname> and search domains listed in <varname>Domains=</varname>. Defaults to
3600 seconds (one hour).</para></listitem>
3600 seconds (one hour).</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@ -4051,6 +4159,8 @@ ServerAddress=192.168.0.1/24</programlisting>
<term><varname>MACAddress=</varname></term>
<listitem>
<para>As in the [Network] section. This key is mandatory.</para>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
<varlistentry>
@ -4125,6 +4235,8 @@ ServerAddress=192.168.0.1/24</programlisting>
<term><varname>VLANId=</varname></term>
<listitem>
<para>The VLAN ID for the new entry. Valid ranges are 0 (no VLAN) to 4094. Optional, defaults to 0.</para>
<xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
</variablelist>
@ -4356,6 +4468,8 @@ ServerAddress=192.168.0.1/24</programlisting>
<listitem>
<para>Specifies the parent Queueing Discipline (qdisc). Takes one of <literal>clsact</literal>
or <literal>ingress</literal>. This is mandatory.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
@ -5334,7 +5448,7 @@ ServerAddress=192.168.0.1/24</programlisting>
Kilobytes, Megabytes, or Gigabytes, respectively, to the base of 1024. Defaults to unset and
kernel's default is used.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
<xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
@ -5622,6 +5736,8 @@ ServerAddress=192.168.0.1/24</programlisting>
<listitem>
<para>The VLAN ID allowed on the port. This can be either a single ID or a range M-N. Takes
an integer in the range 1…4094.</para>
<xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
<varlistentry>

74
man/systemd.resource-control.xml
View File

@ -195,6 +195,8 @@ CPUWeight=20 DisableControllers=cpu / \
<para>Under the unified cgroup hierarchy, CPU accounting is available for all units and this
setting has no effect.</para>
<xi:include href="version-info.xml" xpointer="v208"/>
</listitem>
</varlistentry>
@ -238,6 +240,8 @@ CPUWeight=20 DisableControllers=cpu / \
project='man-pages'><refentrytitle>sched</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
The effect of this feature is similar to the <option>cpu</option> controller with no explicit
configuration, so users should be careful to not mistake one for the other.</para>
<xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
@ -259,6 +263,8 @@ CPUWeight=20 DisableControllers=cpu / \
<para>Example: <varname>CPUQuota=20%</varname> ensures that the executed processes will never get more than
20% CPU time on one CPU.</para>
<xi:include href="version-info.xml" xpointer="v213"/>
</listitem>
</varlistentry>
@ -280,6 +286,8 @@ CPUWeight=20 DisableControllers=cpu / \
<ulink url="https://docs.kernel.org/scheduler/sched-design-CFS.html">CFS Scheduler</ulink>.</para>
<para>Example: <varname>CPUQuotaPeriodSec=10ms</varname> to request that the CPU quota is measured in periods of 10ms.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@ -303,6 +311,8 @@ CPUWeight=20 DisableControllers=cpu / \
boot-up and shutdown differently than during normal runtime.</para>
<para>This setting is supported only with the unified control group hierarchy.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
@ -326,6 +336,8 @@ CPUWeight=20 DisableControllers=cpu / \
for this setting may be controlled with
<varname>DefaultMemoryAccounting=</varname> in
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v208"/>
</listitem>
</varlistentry>
@ -372,6 +384,8 @@ CPUWeight=20 DisableControllers=cpu / \
<varname>MemoryMin=</varname> applies to normal runtime of the system, and if the former is not set also to
the startup and shutdown phases. Using <varname>StartupMemoryLow=</varname> allows prioritizing specific services at
boot-up and shutdown differently than during normal runtime.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
@ -398,6 +412,8 @@ CPUWeight=20 DisableControllers=cpu / \
<varname>MemoryHigh=</varname> applies to normal runtime of the system, and if the former is not set also to
the startup and shutdown phases. Using <varname>StartupMemoryHigh=</varname> allows prioritizing specific services at
boot-up and shutdown differently than during normal runtime.</para>
<xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
@ -424,6 +440,8 @@ CPUWeight=20 DisableControllers=cpu / \
<varname>MemoryMax=</varname> applies to normal runtime of the system, and if the former is not set also to
the startup and shutdown phases. Using <varname>StartupMemoryMax=</varname> allows prioritizing specific services at
boot-up and shutdown differently than during normal runtime.</para>
<xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
@ -446,6 +464,8 @@ CPUWeight=20 DisableControllers=cpu / \
<varname>MemorySwapMax=</varname> applies to normal runtime of the system, and if the former is not set also to
the startup and shutdown phases. Using <varname>StartupMemorySwapMax=</varname> allows prioritizing specific services at
boot-up and shutdown differently than during normal runtime.</para>
<xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
@ -472,6 +492,8 @@ CPUWeight=20 DisableControllers=cpu / \
<varname>MemoryZSwapMax=</varname> applies to normal runtime of the system, and if the former is not set also to
the startup and shutdown phases. Using <varname>StartupMemoryZSwapMax=</varname> allows prioritizing specific services at
boot-up and shutdown differently than during normal runtime.</para>
<xi:include href="version-info.xml" xpointer="v253"/>
</listitem>
</varlistentry>
@ -496,6 +518,8 @@ CPUWeight=20 DisableControllers=cpu / \
boot-up and shutdown differently than during normal runtime.</para>
<para>This setting is supported only with the unified control group hierarchy.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
@ -518,6 +542,8 @@ CPUWeight=20 DisableControllers=cpu / \
slice and for all its parent slices and the units contained therein. The system default for this
setting may be controlled with <varname>DefaultTasksAccounting=</varname> in
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v227"/>
</listitem>
</varlistentry>
@ -539,6 +565,8 @@ CPUWeight=20 DisableControllers=cpu / \
<para>The system default for this setting may be controlled with
<varname>DefaultTasksMax=</varname> in
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v227"/>
</listitem>
</varlistentry>
@ -560,6 +588,8 @@ CPUWeight=20 DisableControllers=cpu / \
therein. The system default for this setting may be controlled with <varname>DefaultIOAccounting=</varname>
in
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -585,6 +615,8 @@ CPUWeight=20 DisableControllers=cpu / \
the system, and if the former is not set also to the startup
and shutdown phases. This allows prioritizing specific services at boot-up
and shutdown differently than during runtime.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -610,6 +642,8 @@ CPUWeight=20 DisableControllers=cpu / \
correctly only for simpler cases, where the file system is directly placed on a partition or
physical block device, or where simple 1:1 encryption using dm-crypt/LUKS is used. This discovery
does not cover complex storage and in particular RAID and volume management storage devices.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -634,6 +668,8 @@ CPUWeight=20 DisableControllers=cpu / \
</para>
<para>Similar restrictions on block device discovery as for <varname>IODeviceWeight=</varname> apply, see above.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -658,6 +694,8 @@ CPUWeight=20 DisableControllers=cpu / \
</para>
<para>Similar restrictions on block device discovery as for <varname>IODeviceWeight=</varname> apply, see above.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@ -681,6 +719,8 @@ CPUWeight=20 DisableControllers=cpu / \
<para>These settings are supported only if the unified control group hierarchy is used.</para>
<para>Similar restrictions on block device discovery as for <varname>IODeviceWeight=</varname> apply, see above.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
@ -708,6 +748,8 @@ CPUWeight=20 DisableControllers=cpu / \
<para>The system default for this setting may be controlled with <varname>DefaultIPAccounting=</varname> in
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@ -813,6 +855,8 @@ CPUWeight=20 DisableControllers=cpu / \
them for IP security.</para>
<xi:include href="cgroup-sandboxing.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@ -906,6 +950,8 @@ SocketBindDeny=any
…</programlisting></para>
<xi:include href="cgroup-sandboxing.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
@ -954,6 +1000,8 @@ RestrictNetworkInterfaces=~eth1</programlisting>
</para>
<xi:include href="cgroup-sandboxing.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
@ -999,6 +1047,8 @@ RestrictNetworkInterfaces=~eth1</programlisting>
support is not enabled in the underlying kernel or container manager). These settings will fail the service in
that case. If compatibility with such systems is desired it is hence recommended to attach your filter manually
(requires <varname>Delegate=</varname><constant>yes</constant>) instead of using this setting.</para>
<xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
@ -1050,6 +1100,8 @@ RestrictNetworkInterfaces=~eth1</programlisting>
<para>Examples:<programlisting>BPFProgram=egress:/sys/fs/bpf/egress-hook
BPFProgram=bind6:/sys/fs/bpf/sock-addr-hook
</programlisting></para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
@ -1109,6 +1161,8 @@ DeviceAllow=/dev/loop-control
…</programlisting></para>
<xi:include href="cgroup-sandboxing.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v208"/>
</listitem>
</varlistentry>
@ -1125,6 +1179,8 @@ DeviceAllow=/dev/loop-control
<listitem>
<para>means to only allow types of access that are
explicitly specified.</para>
<xi:include href="version-info.xml" xpointer="v208"/>
</listitem>
</varlistentry>
@ -1139,6 +1195,8 @@ DeviceAllow=/dev/loop-control
<filename>/dev/random</filename>, and
<filename>/dev/urandom</filename>.
</para>
<xi:include href="version-info.xml" xpointer="v208"/>
</listitem>
</varlistentry>
@ -1150,11 +1208,15 @@ DeviceAllow=/dev/loop-control
explicit <varname>DeviceAllow=</varname> is present.
This is the default.
</para>
<xi:include href="version-info.xml" xpointer="v208"/>
</listitem>
</varlistentry>
</variablelist>
<xi:include href="cgroup-sandboxing.xml" xpointer="singular"/>
<xi:include href="version-info.xml" xpointer="v208"/>
</listitem>
</varlistentry>
@ -1189,6 +1251,8 @@ DeviceAllow=/dev/loop-control
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>, section
"Default Dependencies" for details.</para>
<xi:include href="version-info.xml" xpointer="v208"/>
</listitem>
</varlistentry>
@ -1234,6 +1298,8 @@ DeviceAllow=/dev/loop-control
<para>For further details on the delegation model consult <ulink
url="https://systemd.io/CGROUP_DELEGATION">Control Group APIs and Delegation</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@ -1281,6 +1347,8 @@ DeviceAllow=/dev/loop-control
of the cgroup hierarchy is unmanaged by systemd.</para>
<xi:include href="supported-controllers.xml" xpointer="controllers-text" />
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
@ -1317,6 +1385,8 @@ DeviceAllow=/dev/loop-control
cgroup's data for monitoring and detection. However, if an ancestor cgroup has one of these
properties set to <option>kill</option>, a unit with <option>auto</option> can still be a candidate
for <command>systemd-oomd</command> to terminate.</para>
<xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
@ -1331,6 +1401,8 @@ DeviceAllow=/dev/loop-control
which means to use the default set by
<citerefentry><refentrytitle>oomd.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
@ -1373,6 +1445,8 @@ DeviceAllow=/dev/loop-control
<citerefentry><refentrytitle>systemd-oomd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
and <citerefentry><refentrytitle>oomd.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>

62
man/systemd.special.xml
View File

@ -127,6 +127,8 @@
<para>The root mount point, i.e. the mount unit for the <filename>/</filename>
path. This unit is unconditionally active, during the entire time the system is up, as
this mount point is where the basic userspace is running from.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@ -177,6 +179,8 @@
<citerefentry><refentrytitle>systemd-bless-boot.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for a service that propagates boot success information to the boot loader, and orders itself after
<filename>boot-complete.target</filename>.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
<varlistentry>
@ -283,6 +287,8 @@
<filename>shutdown.target</filename>, which in turn should be
conflicted by all units that want to be scheduled for
shutdown when the service manager starts to exit.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
<varlistentry>
@ -339,6 +345,8 @@
<para>A special target unit for hibernating and suspending
the system at the same time. This pulls in
<filename>sleep.target</filename>.</para>
<xi:include href="version-info.xml" xpointer="v196"/>
</listitem>
</varlistentry>
<varlistentry>
@ -347,6 +355,8 @@
<para>A special target unit for suspending the system for a period
of time, waking it and putting it into hibernate. This pulls in
<filename>sleep.target</filename>.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@ -372,6 +382,8 @@
<listitem>
<para>This scope unit is where the system and service manager (PID 1) itself resides. It
is active as long as the system is running.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<varlistentry>
@ -381,6 +393,8 @@
the main system. It is used to mount the real root and transition to it. See
<citerefentry><refentrytitle>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
more discussion.</para>
<xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<varlistentry>
@ -394,6 +408,8 @@
<filename>sysroot.mount</filename>. Thus, once this target is reached the
<filename>/sysroot/</filename> hierarchy is fully set up, in preparation for the transition to
the host OS.</para>
<xi:include href="version-info.xml" xpointer="v199"/>
</listitem>
</varlistentry>
<varlistentry>
@ -406,6 +422,8 @@
<citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>
automatically setup the appropriate dependencies to make this happen.
</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
<varlistentry>
@ -415,6 +433,8 @@
automatically adds dependencies of type <varname>Before=</varname> to the
<filename>sysroot.mount</filename> unit, which is generated from the kernel command line's
<varname>root=</varname> setting (or equivalent).</para>
<xi:include href="version-info.xml" xpointer="v199"/>
</listitem>
</varlistentry>
<varlistentry>
@ -482,6 +502,8 @@
<para>A standard target unit for starting all the containers
and other virtual machines. See <filename>systemd-nspawn@.service</filename>
for an example.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
<varlistentry>
@ -533,6 +555,8 @@
logic. After the system has completed booting up, it will not track the online state of
the system anymore. Due to this it cannot be used as a network connection monitor
concept, it is purely a one-time system start-up concept.</para>
<xi:include href="version-info.xml" xpointer="v200"/>
</listitem>
</varlistentry>
<varlistentry>
@ -547,6 +571,8 @@
dependencies from this unit. This is best configured via a
<varname>WantedBy=paths.target</varname> in the path unit's
[Install] section.</para>
<xi:include href="version-info.xml" xpointer="v199"/>
</listitem>
</varlistentry>
<varlistentry>
@ -592,6 +618,8 @@
devices which are accessed over the network. It is used for
<citerefentry><refentrytitle>crypttab</refentrytitle><manvolnum>8</manvolnum></citerefentry>
entries marked with <option>_netdev</option>.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<varlistentry>
@ -699,6 +727,8 @@
section should only be done for units that need to be always active. In that case care
needs to be taken to avoid creating a loop through the automatic dependencies on
"parent" slices.</para>
<xi:include href="version-info.xml" xpointer="v229"/>
</listitem>
</varlistentry>
<varlistentry>
@ -803,6 +833,8 @@
<filename>system-update.target</filename> is reached,
<filename>system-update-cleanup.service</filename> will remove the symlinks and reboot
the machine.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
<varlistentry>
@ -818,6 +850,8 @@
dependencies from this unit. This is best configured via
<varname>WantedBy=timers.target</varname> in the timer
unit's [Install] section.</para>
<xi:include href="version-info.xml" xpointer="v199"/>
</listitem>
</varlistentry>
<varlistentry>
@ -897,6 +931,8 @@
<para>This may be used to pull in usb gadget
dynamically when UDC hardware is found.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
</variablelist>
@ -939,7 +975,9 @@
part of any transaction unless a storage daemon is used. The instance name for instances of this
template unit must be a properly escaped block device node path, e.g.
<filename index="false">blockdev@dev-mapper-foobar.target</filename> for the storage device
<filename index="false">/dev/mapper/foobar</filename>.</para></listitem>
<filename index="false">/dev/mapper/foobar</filename>.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
<term><filename>cryptsetup-pre.target</filename></term>
@ -952,6 +990,8 @@
particularly useful to ensure that a service is shut down
only after all encrypted block devices are fully
stopped.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
<varlistentry>
@ -991,6 +1031,8 @@
unit before this unit if you want to make use of the console
just before <filename>getty</filename> is started.
</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<varlistentry>
@ -1041,6 +1083,8 @@
orders itself after this target, but does not pull it in. Also see <ulink
url="https://systemd.io/NETWORK_ONLINE">Running Services After the Network Is Up</ulink> for more
information.</para>
<xi:include href="version-info.xml" xpointer="v214"/>
</listitem>
</varlistentry>
<varlistentry>
@ -1128,6 +1172,8 @@
monotonic. Enable
<citerefentry><refentrytitle>systemd-timesyncd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
or an alternative NTP implementation to delay the target.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<varlistentry>
@ -1215,6 +1261,8 @@
<listitem>
<para>The root slice is the root of the slice hierarchy. It usually does not contain
units directly, but may be used to set defaults for the whole tree.</para>
<xi:include href="version-info.xml" xpointer="v206"/>
</listitem>
</varlistentry>
@ -1223,6 +1271,8 @@
<listitem>
<para>By default, all system services started by
<command>systemd</command> are found in this slice.</para>
<xi:include href="version-info.xml" xpointer="v206"/>
</listitem>
</varlistentry>
@ -1233,6 +1283,8 @@
behalf of the user, including the per-user systemd instance
are found in this slice. This is pulled in by
<filename>systemd-logind.service</filename>.</para>
<xi:include href="version-info.xml" xpointer="v206"/>
</listitem>
</varlistentry>
@ -1243,6 +1295,8 @@
registered with <command>systemd-machined</command> are
found in this slice. This is pulled in by
<filename>systemd-machined.service</filename>.</para>
<xi:include href="version-info.xml" xpointer="v206"/>
</listitem>
</varlistentry>
</variablelist>
@ -1266,6 +1320,8 @@
compose the normal user session should be pulled into this target. In this regard,
<filename>default.target</filename> is similar to <filename>multi-user.target</filename> in the
system instance, but it is a real unit, not an alias.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
</variablelist>
@ -1328,6 +1384,8 @@ PartOf=graphical-session.target
[Service]
…</programlisting>
</example>
<xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
@ -1340,6 +1398,8 @@ PartOf=graphical-session.target
upgrade (which needs to happen before starting any process that might use them). This
target must be started before starting a graphical session like
<filename>gnome-session.target</filename>.</para>
<xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>

2
man/systemd.swap.xml
View File

@ -141,6 +141,8 @@
<filename>swap.target</filename>. This means that the boot
will continue even if this swap device is not activated
successfully.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>

2
man/systemd.system-credentials.xml
View File

@ -61,6 +61,8 @@
and only honoured if no locale has been configured before. <varname>firstboot.locale</varname> sets
<literal>LANG</literal>, while <varname>firstboot.locale-message</varname> sets
<literal>LC_MESSAGES</literal>.</para>
<xi:include href="version-info.xml" xpointer="v252"/>
</listitem>
</varlistentry>

92
man/systemd.unit.xml
View File

@ -600,6 +600,8 @@
<replaceable>description</replaceable>.</literal>), so it should be capitalized, and should not be a
full sentence, or a phrase with a continuous verb. Bad examples include <literal>exiting the
container</literal> or <literal>updating the database once per day.</literal>.</para>
<xi:include href="version-info.xml" xpointer="v201"/>
</listitem>
</varlistentry>
@ -620,7 +622,9 @@
once, in which case the specified list of URIs is merged. If
the empty string is assigned to this option, the list is reset
and all prior assignments will have no
effect.</para></listitem>
effect.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -643,7 +647,9 @@
<filename>bar.service</filename> as configured with <varname>Wants=</varname> and no ordering is
configured with <varname>After=</varname> or <varname>Before=</varname>, then both units will be
started simultaneously and without any delay between them if <filename>foo.service</filename> is
activated.</para></listitem>
activated.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -670,7 +676,9 @@
example, a service process may decide to exit cleanly, or a device may be unplugged by the user), which is not
propagated to units having a <varname>Requires=</varname> dependency. Use the <varname>BindsTo=</varname>
dependency type together with <varname>After=</varname> to ensure that a unit may never be in active state
without a specific other unit also in active state (see below).</para></listitem>
without a specific other unit also in active state (see below).</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -688,6 +696,8 @@
<varname>RequisiteOf=a.service</varname> in property listing of
<filename>b.service</filename>. <varname>RequisiteOf=</varname>
dependency cannot be specified directly.</para>
<xi:include href="version-info.xml" xpointer="v201"/>
</listitem>
</varlistentry>
@ -715,6 +725,8 @@
<varname>BoundBy=a.service</varname> in property listing of
<filename>b.service</filename>. <varname>BoundBy=</varname>
dependency cannot be specified directly.</para>
<xi:include href="version-info.xml" xpointer="v201"/>
</listitem>
</varlistentry>
@ -733,6 +745,8 @@
<varname>ConsistsOf=a.service</varname> in property listing of
<filename>b.service</filename>. <varname>ConsistsOf=</varname>
dependency cannot be specified directly.</para>
<xi:include href="version-info.xml" xpointer="v201"/>
</listitem>
</varlistentry>
@ -776,7 +790,9 @@
required part of the transaction). In the latter case, the job
that is not required will be removed, or in case both are
not required, the unit that conflicts will be started and the
unit that is conflicted is stopped.</para></listitem>
unit that is conflicted is stopped.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -817,14 +833,18 @@
<para>Note that <varname>Before=</varname> dependencies on device units have no effect and are not
supported. Devices generally become available as a result of an external hotplug event, and systemd
creates the corresponding device unit without delay.</para></listitem>
creates the corresponding device unit without delay.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>OnFailure=</varname></term>
<listitem><para>A space-separated list of one or more units that are activated when this unit enters
the <literal>failed</literal> state.</para></listitem>
the <literal>failed</literal> state.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -843,7 +863,9 @@
<listitem><para>A space-separated list of one or more units to which reload requests from this unit
shall be propagated to, or units from which reload requests shall be propagated to this unit,
respectively. Issuing a reload request on a unit will automatically also enqueue reload requests on
all units that are linked to it using these two settings.</para></listitem>
all units that are linked to it using these two settings.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -876,7 +898,9 @@
effect if <varname>PrivateNetwork=</varname>/<varname>NetworkNamespacePath=</varname>,
<varname>PrivateIPC=</varname>/<varname>IPCNamespacePath=</varname> and/or
<varname>PrivateTmp=</varname> is enabled for both the unit that joins the namespace and the unit
whose namespace is joined.</para></listitem>
whose namespace is joined.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -890,7 +914,9 @@
<para>Mount points marked with <option>noauto</option> are not
mounted automatically through <filename>local-fs.target</filename>,
but are still honored for the purposes of this option, i.e. they
will be pulled in by this unit.</para></listitem>
will be pulled in by this unit.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -911,7 +937,9 @@
<option>--job-mode=</option> option for details on the
possible values. If this is set to <literal>isolate</literal>,
only a single unit may be listed in
<varname>OnSuccess=</varname>/<varname>OnFailure=</varname>.</para></listitem>
<varname>OnSuccess=</varname>/<varname>OnFailure=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@ -920,7 +948,9 @@
<listitem><para>Takes a boolean argument. If <option>true</option>, this unit will not be stopped
when isolating another unit. Defaults to <option>false</option> for service, target, socket, timer,
and path units, and <option>true</option> for slice, scope, device, swap, mount, and automount
units.</para></listitem>
units.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -933,7 +963,9 @@
are conflicting with other units, or the user explicitly
requested their shut down. If this option is set, a unit will
be automatically cleaned up if no other active unit requires
it. Defaults to <option>false</option>.</para></listitem>
it. Defaults to <option>false</option>.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -950,7 +982,9 @@
that are not intended to be activated explicitly, and not
accidentally deactivate units that are not intended to be
deactivated. These options default to
<option>false</option>.</para></listitem>
<option>false</option>.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -963,7 +997,9 @@
disabled except for target units that shall be used similar to
runlevels in SysV init systems, just as a precaution to avoid
unusable system states. This option defaults to
<option>false</option>.</para></listitem>
<option>false</option>.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -982,7 +1018,9 @@
leave this option enabled for the majority of common units. If
set to <option>no</option>, this option does not disable
all implicit dependencies, just non-essential
ones.</para></listitem>
ones.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -1080,6 +1118,8 @@
unit itself. Or in other words: unit-specific timeouts are useful to abort unit state changes, and
revert them. The job timeout set with this option however is useful to abort only the job waiting for
the unit state to change.</para>
<xi:include href="version-info.xml" xpointer="v201"/>
</listitem>
</varlistentry>
@ -1138,7 +1178,7 @@
<para>This setting does not apply to slice, target, device, and scope units, since they are unit
types whose activation may either never fail, or may succeed only a single time.</para>
<xi:include href="version-info.xml" xpointer="v236"/></listitem>
<xi:include href="version-info.xml" xpointer="v229"/></listitem>
</varlistentry>
<varlistentry>
@ -1170,7 +1210,9 @@
implementation of generator tools that convert configuration
from an external configuration file format into native unit
files. This functionality should not be used in normal
units.</para></listitem>
units.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
</variablelist>
@ -1261,6 +1303,8 @@
condition. A special architecture name <literal>native</literal> is mapped to the architecture the
system manager itself is compiled for. The test may be negated by prepending an exclamation
mark.</para>
<xi:include href="version-info.xml" xpointer="v201"/>
</listitem>
</varlistentry>
@ -1884,6 +1928,8 @@
only the job queued for it. Use assertion expressions for units that cannot operate when specific
requirements are not met, and when this is something the administrator or user should look
into.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
</variablelist>
@ -2039,7 +2085,9 @@
in which case all listed names are used. At installation time, <command>systemctl enable</command> will create
symlinks from these names to the unit filename. Note that not all unit types support such alias names, and this
setting is not supported for them. Specifically, mount, slice, swap, and automount units do not support
aliasing.</para></listitem>
aliasing.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -2070,7 +2118,9 @@
result in <command>systemctl enable monitor@.service</command> creating a
<filename>container@.target.wants/monitor@.service</filename> link to
<filename>monitor@.service</filename>, which applies to all instances of
<filename>container@.target</filename>.</para></listitem>
<filename>container@.target</filename>.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>
@ -2085,7 +2135,9 @@
<para>This option may be used more than once, or a
space-separated list of unit names may be
given.</para></listitem>
given.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
<varlistentry>

36
man/systemd.xml
View File

@ -640,7 +640,9 @@
<listitem><para>Sets the log target to <literal>console</literal> on <constant>SIGRTMIN+27</constant> (or
<literal>kmsg</literal> on <constant>SIGRTMIN+28</constant>), in a fashion equivalent to
<varname>systemd.log_target=console</varname> (or <varname>systemd.log_target=kmsg</varname> on
<constant>SIGRTMIN+28</constant>) on the kernel command line.</para></listitem>
<constant>SIGRTMIN+28</constant>) on the kernel command line.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@ -851,7 +853,7 @@
reboot loop. If combined with <varname>systemd.crash_shell</varname>, the
system is rebooted after the shell exits.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v227"/></listitem>
</varlistentry>
<varlistentry>
@ -985,7 +987,9 @@
keys), or in testing/debugging environments.</para>
<para>For further information see <ulink url="https://systemd.io/CREDENTIALS">System and Service
Credentials</ulink> documentation.</para></listitem>
Credentials</ulink> documentation.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
<varlistentry>
@ -1032,7 +1036,9 @@
<listitem><para>Boot into emergency mode. This is equivalent
to <varname>systemd.unit=emergency.target</varname> or
<varname>rd.systemd.unit=emergency.target</varname>, respectively, and
provided for compatibility reasons and to be easier to type.</para></listitem>
provided for compatibility reasons and to be easier to type.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -1046,7 +1052,9 @@
<listitem><para>Boot into rescue mode. This is equivalent to
<varname>systemd.unit=rescue.target</varname> or
<varname>rd.systemd.unit=rescue.target</varname>, respectively, and
provided for compatibility reasons and to be easier to type.</para></listitem>
provided for compatibility reasons and to be easier to type.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@ -1198,7 +1206,9 @@
<term><option>--dump-bus-properties</option></term>
<listitem><para>Dump exposed bus properties. This outputs a terse but complete list of properties
exposed on D-Bus.</para></listitem>
exposed on D-Bus.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@ -1270,7 +1280,9 @@
<listitem><para>Switch to a specific virtual console (VT) on crash. This switch has no effect when
running as user instance. Same as <varname>systemd.crash_chvt=</varname> above (but not the
different spelling!).</para></listitem>
different spelling!).</para>
<xi:include href="version-info.xml" xpointer="v227"/></listitem>
</varlistentry>
<varlistentry>
@ -1284,7 +1296,9 @@
<term><option>--crash-reboot</option></term>
<listitem><para>Automatically reboot the system on crash. This switch has no effect when running as
user instance. See <varname>systemd.crash_reboot</varname> above.</para></listitem>
user instance. See <varname>systemd.crash_reboot</varname> above.</para>
<xi:include href="version-info.xml" xpointer="v227"/></listitem>
</varlistentry>
<varlistentry>
@ -1346,7 +1360,9 @@
<term><option>--machine-id=</option></term>
<listitem><para>Override the machine-id set on the hard drive. See
<varname>systemd.machine_id=</varname> above.</para></listitem>
<varname>systemd.machine_id=</varname> above.</para>
<xi:include href="version-info.xml" xpointer="v229"/></listitem>
</varlistentry>
<varlistentry>
@ -1355,7 +1371,7 @@
<listitem><para>Globally enable/disable all service watchdog timeouts and emergency actions. See
<varname>systemd.service_watchdogs</varname> above.</para>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
<xi:include href="version-info.xml" xpointer="v237"/></listitem>
</varlistentry>
<varlistentry>

16
man/sysusers.d.xml
View File

@ -114,7 +114,9 @@ r - 500-900
<listitem><para>Create a system user and group of the specified name should
they not exist yet. The user's primary group will be set to the group
bearing the same name unless the ID field specifies it. The account will be
created disabled, so that logins are not allowed.</para></listitem>
created disabled, so that logins are not allowed.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -122,14 +124,18 @@ r - 500-900
<listitem><para>Create a system group of the specified name
should it not exist yet. Note that <varname>u</varname>
implicitly creates a matching group. The group will be
created with no password set.</para></listitem>
created with no password set.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>m</varname></term>
<listitem><para>Add a user to a group. If the user or group
do not exist yet, they will be implicitly
created.</para></listitem>
created.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@ -140,7 +146,9 @@ r - 500-900
compiled-in default. Note that both UIDs and GIDs are
allocated from the same pool, in order to ensure that users
and groups of the same name are likely to carry the same
numeric UID and GID.</para></listitem>
numeric UID and GID.</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
</variablelist>

28
man/timedatectl.xml
View File

@ -58,7 +58,9 @@
<listitem><para>Show current settings of the system clock and RTC, including whether network time
synchronization is active. If no command is specified, this is the implied default.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -79,7 +81,9 @@
<listitem><para>Set the system clock to the specified time.
This will also update the RTC time accordingly. The time may
be specified in the format "2012-10-30
18:17:16".</para></listitem>
18:17:16".</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -92,7 +96,9 @@
call will alter the <filename>/etc/localtime</filename>
symlink. See
<citerefentry><refentrytitle>localtime</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for more information.</para></listitem>
for more information.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -100,7 +106,9 @@
<listitem><para>List available time zones, one per line.
Entries from the list can be set as the system timezone with
<command>set-timezone</command>.</para></listitem>
<command>set-timezone</command>.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -119,7 +127,9 @@
This command will change the 3rd line of
<filename>/etc/adjtime</filename>, as documented in
<citerefentry project='man-pages'><refentrytitle>hwclock</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@ -130,7 +140,9 @@
synchronization service. If the argument is false, then this disables and stops the known network
synchronization services. The way that the list of services is built is described in
<citerefentry><refentrytitle>systemd-timedated.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
</variablelist>
@ -233,7 +245,9 @@
<listitem><para>When showing properties of
<citerefentry><refentrytitle>systemd-timesyncd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
show all properties regardless of whether they are set or not.</para></listitem>
show all properties regardless of whether they are set or not.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>

44
man/tmpfiles.d.xml
View File

@ -214,7 +214,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
<para>For this entry to be useful, at least one of the mode, user, group, or age arguments must be
specified, since otherwise this entry has no effect. As an exception, an entry with no effect may
be useful when combined with <varname>!</varname>, see the examples.</para></listitem>
be useful when combined with <varname>!</varname>, see the examples.</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@ -226,7 +228,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
<para>A subvolume created with this line type is not assigned to any higher-level quota group. For
that, use <varname>q</varname> or <varname>Q</varname>, which allow creating simple quota group
hierarchies, see below.</para></listitem>
hierarchies, see below.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -239,7 +243,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
<para>If the subvolume already exists, no change to the quota hierarchy is made, regardless of whether the
subvolume is already attached to a quota group or not. Also see <varname>Q</varname> below. See <citerefentry
project='die-net'><refentrytitle>btrfs-qgroup</refentrytitle><manvolnum>8</manvolnum></citerefentry> for
details about the btrfs quota group concept.</para></listitem>
details about the btrfs quota group concept.</para>
<xi:include href="version-info.xml" xpointer="v228"/></listitem>
</varlistentry>
<varlistentry>
@ -273,7 +279,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
<para>As with <varname>q</varname>, <varname>Q</varname> has no effect on the quota group hierarchy if the
subvolume already exists, regardless of whether the subvolume already belong to a quota group or not.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v228"/></listitem>
</varlistentry>
<varlistentry>
@ -335,7 +343,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
is omitted, files from the source directory <filename>/usr/share/factory/</filename> with the same
name are copied. Does not follow symlinks. Contents of the directories are subject to time-based
cleanup if the age argument is specified.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v214"/></listitem>
</varlistentry>
<varlistentry>
@ -358,7 +368,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
influence the effect of <varname>r</varname> or
<varname>R</varname> lines. Lines of this type accept
shell-style globs in place of normal path names.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v198"/></listitem>
</varlistentry>
<varlistentry>
@ -405,12 +417,16 @@ L /tmp/foobar - - - - /dev/null</programlisting>
<para>Please note that extended attributes settable with this line type are a different concept
from the Linux file attributes settable with <varname>h</varname>/<varname>H</varname>, see
below.</para></listitem>
below.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>T</varname></term>
<listitem><para>Same as <varname>t</varname>, but operates recursively.</para></listitem>
<listitem><para>Same as <varname>t</varname>, but operates recursively.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -438,7 +454,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
<varlistentry>
<term><varname>H</varname></term>
<listitem><para>Sames as <varname>h</varname>, but operates recursively.</para></listitem>
<listitem><para>Sames as <varname>h</varname>, but operates recursively.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
@ -455,7 +473,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
file, unless base entries already exist or are explicitly specified. The mask will be added if not
specified explicitly or already present. Lines of this type accept shell-style globs in place of
normal path names. This can be useful for allowing additional access to certain files. Does not
follow symlinks.</para></listitem>
follow symlinks.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@ -463,7 +483,9 @@ L /tmp/foobar - - - - /dev/null</programlisting>
<term><varname>A+</varname></term>
<listitem><para>Same as <varname>a</varname> and
<varname>a+</varname>, but recursive. Does not follow
symlinks.</para></listitem>
symlinks.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
</variablelist>
</refsect2>

2
man/udev.conf.xml
View File

@ -47,7 +47,7 @@
<option>err</option>, <option>info</option> and
<option>debug</option>.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
<xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>

24
man/udev.xml
View File

@ -111,6 +111,8 @@
<term><literal>-=</literal></term>
<listitem>
<para>Remove the value from a key that holds a list of entries.</para>
<xi:include href="version-info.xml" xpointer="v217"/>
</listitem>
</varlistentry>
@ -250,6 +252,8 @@
<term><varname>SYSCTL{<replaceable>kernel parameter</replaceable>}</varname></term>
<listitem>
<para>Match a kernel parameter value.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
@ -271,6 +275,8 @@
<para>System's architecture. See <option>ConditionArchitecture=</option> in
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for possible values.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<varlistentry>
@ -279,6 +285,8 @@
<para>System's virtualization environment. See
<citerefentry><refentrytitle>systemd-detect-virt</refentrytitle><manvolnum>1</manvolnum></citerefentry>
for possible values.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<varlistentry>
@ -293,6 +301,8 @@
</varlistentry>
</variablelist>
<para>Unknown keys will never match.</para>
<xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
@ -382,6 +392,8 @@
<para>Separates alternative patterns. For example, the pattern string
<literal>abc|x*</literal> would match either <literal>abc</literal>
or <literal>x*</literal>.</para>
<xi:include href="version-info.xml" xpointer="v217"/>
</listitem>
</varlistentry>
</variablelist>
@ -433,6 +445,8 @@
<term><varname>SECLABEL{<replaceable>module</replaceable>}</varname></term>
<listitem>
<para>Applies the specified Linux Security Module label to the device node.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@ -448,6 +462,8 @@
<term><varname>SYSCTL{<replaceable>kernel parameter</replaceable>}</varname></term>
<listitem>
<para>The value that should be written to kernel parameter.</para>
<xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
@ -502,6 +518,8 @@
<listitem>
<para>As <varname>program</varname>, but use one of the
built-in programs rather than an external one.</para>
<xi:include href="version-info.xml" xpointer="v199"/>
</listitem>
</varlistentry>
</variablelist>
@ -554,6 +572,8 @@
import its output, which must be in environment key
format. Path specification, command/argument separation,
and quoting work like in <varname>RUN</varname>.</para>
<xi:include href="version-info.xml" xpointer="v199"/>
</listitem>
</varlistentry>
<varlistentry>
@ -561,6 +581,8 @@
<listitem>
<para>Similar to <literal>program</literal>, but use one of the
built-in programs rather than an external one.</para>
<xi:include href="version-info.xml" xpointer="v199"/>
</listitem>
</varlistentry>
<varlistentry>
@ -667,6 +689,8 @@
--cleanup-db</command> is called. This option can be useful in certain cases
(e.g. Device Mapper devices) for persisting device state on the transition from
initrd.</para>
<xi:include href="version-info.xml" xpointer="v241"/>
</listitem>
</varlistentry>
<varlistentry>

8
man/udevadm.xml
View File

@ -450,6 +450,8 @@
<listitem>
<para>Trigger events for devices with a matching device path. When this option is specified more than once,
then each matching result is ORed, that is, all specified devices are triggered.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
<varlistentry>
@ -494,6 +496,8 @@
settle</command>. <command>udevadm settle</command> waits for all
events to finish. This option only waits for events triggered by
the same command to finish.</para>
<xi:include href="version-info.xml" xpointer="v238"/>
</listitem>
</varlistentry>
<varlistentry>
@ -730,6 +734,8 @@
be resolved for every event. When set to
<constant>never</constant>, names will never be resolved
and all devices will be owned by root.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@ -755,6 +761,8 @@
<literal>online</literal>, <literal>offline</literal>, <literal>bind</literal>,
and <literal>unbind</literal>. Also, the special value <literal>help</literal> can be used
to list the possible actions. The default value is <literal>add</literal>.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>

70
man/ukify.xml
View File

@ -190,7 +190,9 @@
<listitem><para>Enable or disable a call to
<citerefentry><refentrytitle>systemd-measure</refentrytitle><manvolnum>1</manvolnum></citerefentry>
to print pre-calculated PCR values. Defaults to false.</para></listitem>
to print pre-calculated PCR values. Defaults to false.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -212,7 +214,7 @@
<para>Note that the name is used as-is, and if the section name should start with a dot, it must be
included in <replaceable>NAME</replaceable>.</para>
<xi:include href="version-info.xml" xpointer="v255"/>
<xi:include href="version-info.xml" xpointer="v253"/>
</listitem>
</varlistentry>
@ -221,7 +223,9 @@
<listitem><para>Specify one or more directories with helper tools. <command>ukify</command> will
look for helper tools in those directories first, and if not found, try to load them from
<varname>$PATH</varname> in the usual fashion.</para></listitem>
<varname>$PATH</varname> in the usual fashion.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -230,7 +234,9 @@
<listitem><para>The output filename. If not specified, the name of the
<replaceable>LINUX</replaceable> argument, with the suffix <literal>.unsigned.efi</literal> or
<literal>.signed.efi</literal> will be used, depending on whether signing for SecureBoot was
performed.</para></listitem>
performed.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -293,7 +299,9 @@
<listitem><para>The kernel command line (the <literal>.cmdline</literal> section). The argument may
be a literal string, or <literal>@</literal> followed by a path name. If not specified, no command
line will be embedded.</para></listitem>
line will be embedded.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -303,7 +311,9 @@
<listitem><para>The os-release description (the <literal>.osrel</literal> section). The argument
may be a literal string, or <literal>@</literal> followed by a path name. If not specified, the
<citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry> file
will be picked up from the host system.</para></listitem>
will be picked up from the host system.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -312,7 +322,9 @@
<listitem><para>The devicetree description (the <literal>.dtb</literal> section). The argument is a
path to a compiled binary DeviceTree file. If not specified, the section will not be present.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -321,7 +333,9 @@
<listitem><para>A picture to display during boot (the <literal>.splash</literal> section). The
argument is a path to a BMP file. If not specified, the section will not be present.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -331,7 +345,9 @@
<listitem><para>A path to a public key to embed in the <literal>.pcrpkey</literal> section. If not
specified, and there's exactly one
<varname>PCRPublicKey=</varname>/<option>--pcr-public-key=</option> argument, that key will be used.
Otherwise, the section will not be present.</para></listitem>
Otherwise, the section will not be present.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -342,7 +358,9 @@
<literal>.uname</literal> section). If not specified, an attempt will be made to extract the
version string from the kernel image. It is recommended to pass this explicitly if known, because
the extraction is based on heuristics and not very reliable. If not specified and extraction fails,
the section will not be present.</para></listitem>
the section will not be present.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -352,7 +370,9 @@
<listitem><para>A comma or space-separated list of PCR banks to sign a policy for. If not present,
all known banks will be used (<literal>sha1</literal>, <literal>sha256</literal>,
<literal>sha384</literal>, <literal>sha512</literal>), which will fail if not supported by the
system.</para></listitem>
system.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -373,7 +393,9 @@
<listitem><para>A path to a private key to use for signing of the resulting binary. If the
<varname>SigningEngine=</varname>/<option>--signing-engine=</option> option is used, this may also be
an engine-specific designation. This option is required by
<varname>SecureBootSigningTool=sbsign</varname>/<option>--signtool=sbsign</option>. </para></listitem>
<varname>SecureBootSigningTool=sbsign</varname>/<option>--signtool=sbsign</option>. </para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -383,7 +405,9 @@
<listitem><para>A path to a certificate to use for signing of the resulting binary. If the
<varname>SigningEngine=</varname>/<option>--signing-engine=</option> option is used, this may also
be an engine-specific designation. This option is required by
<varname>SecureBootSigningTool=sbsign</varname>/<option>--signtool=sbsign</option>. </para></listitem>
<varname>SecureBootSigningTool=sbsign</varname>/<option>--signtool=sbsign</option>. </para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -424,7 +448,9 @@
<listitem><para>An "engine" for signing of the resulting binary. This option is currently passed
verbatim to the <option>--engine=</option> option of
<citerefentry project='archlinux'><refentrytitle>sbsign</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -438,7 +464,9 @@
<varname>SecureBootPrivateKey=</varname>/<option>--secureboot-private-key=</option> option and the
binary has not already been signed. If
<varname>SignKernel=</varname>/<option>--sign-kernel</option> is true, and the binary has already
been signed, the signature will be appended anyway.</para></listitem>
been signed, the signature will be appended anyway.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -471,7 +499,9 @@
<term><option>--pcr-private-key=<replaceable>PATH</replaceable></option></term>
<listitem><para>A private key to use for signing PCR policies. On the commandline, this option may
be specified more than once, in which case multiple signatures will be made.</para></listitem>
be specified more than once, in which case multiple signatures will be made.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -483,7 +513,9 @@
<para>On the commandline, this option may be specified more than once, similarly to the
<option>--pcr-private-key=</option> option. If not present, the public keys will be extracted from
the private keys. On the commandline, if present, the this option must be specified the same number
of times as the <option>--pcr-private-key=</option> option.</para></listitem>
of times as the <option>--pcr-private-key=</option> option.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@ -497,7 +529,9 @@
will be used.</para>
<para>On the commandline, when this argument is present, it must appear the same number of times as
the <option>--pcr-private-key=</option> option. </para></listitem>
the <option>--pcr-private-key=</option> option. </para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
</variablelist>
</refsect2>

2
man/userdbctl.xml
View File

@ -318,7 +318,7 @@
data, however the NSS/glibc APIs necessarily expose a more reduced set of fields
only.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>

2
man/veritytab.xml
View File

@ -218,7 +218,7 @@ This is based on crypttab(5).
path to roothash signature file used to verify the root hash (in kernel). This feature requires Linux kernel
version 5.4 or more recent.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>