dasharo/systemd
0
0
Fork 0
mirror of https://github.com/Dasharo/systemd.git synced 2026-03-06 15:02:31 -08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #29882 from keszybz/documentation-cleanup

Browse Source 
Documentation cleanup
This commit is contained in:
Luca Boccassi
2023-11-06 21:24:08 +00:00
committed by GitHub
parent 4457a2e0ee 0155b0657d
commit 4a5bf4896f
47 changed files with 304 additions and 249 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
NEWS
View File

@@ -718,9 +718,9 @@ CHANGES WITH 254:
store enabled.
* A new service option FileDescriptorStorePreserve= has been added that
allows tuning the life-cycle of the per-service file descriptor
store. If set to "yes", the entries in the fd store are retained even
after the service has been fully stopped.
allows tuning the lifecycle of the per-service file descriptor store.
If set to "yes", the entries in the fd store are retained even after
the service has been fully stopped.
* The "systemctl clean" command may now be used to clear the fdstore of
a service.

2
catalog/systemd.catalog.in
View File

@@ -741,7 +741,7 @@ compatibility.
Note that these automatically generated compatibility unit files cannot replace
native unit files as they generally slow down the system (by creating
unnecessary, additional synchronization points), are less robust (as SysV services
cannot properly be life-cycle tracked or automatically restarted) and less
cannot properly be lifecycle tracked or automatically restarted) and less
secure (as no sandboxing restrictions can be enforced).
Compatibility support for System V services in systemd is deprecated. Please

2
docs/BUILDING_IMAGES.md
View File

@@ -5,7 +5,7 @@ layout: default
SPDX-License-Identifier: LGPL-2.1-or-later
---
# Safely Building Images
# Building Images Safely
In many scenarios OS installations are shipped as pre-built images, that
require no further installation process beyond simple `dd`-ing the image to

16
docs/FILE_DESCRIPTOR_STORE.md
View File

@@ -47,7 +47,7 @@ conveniently be used to serialize service state into and then place in the
fdstore, in order to implement service restarts with full service state being
passed over.
# Basic Mechanism
## Basic Mechanism
The fdstore is enabled per-service via the
[`FileDescriptorStoreMax=`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#FileDescriptorStoreMax=)
@@ -76,7 +76,7 @@ both operates on IPv4 and IPv6 and treats both more or less the same.).
And that's already the gist of it.
# Seamless Service Restarts
## Seamless Service Restarts
A system service that provides a client-facing interface that shall be able to
seamlessly restart can make use of this in a scheme like the following:
@@ -100,14 +100,14 @@ general principle of guaranteeing a pristine execution environment, a pristine
security context, and a pristine resource management context for freshly
started services, without uncontrolled "leftovers" from previous runs. For
example: leaving processes from previous runs generally negatively affects
life-cycle management (i.e. `KillMode=none` must be set), which disables large
lifecycle management (i.e. `KillMode=none` must be set), which disables large
parts of the service managers state tracking, resource management (as resource
counters cannot start at zero during service activation anymore, since the old
processes remaining skew them), security policies (as processes with possibly
out-of-date security policies – SElinux, AppArmor, any LSM, seccomp, BPF — in
effect remain), and similar.
# File Descriptor Store Life-cycle
## File Descriptor Store Lifecycle
By default any file descriptor stored in the fdstore for which a `POLLHUP` or
`POLLERR` is seen is automatically closed and removed from the fdstore. This
@@ -148,7 +148,7 @@ way will not receive an automatic `POLLHUP` event anymore if the service code
issues `close()` on the socket. It must accompany it with an `FDSTOREREMOVE=1`
notification to the service manager, so that the fd is comprehensively closed.
# Access Control
## Access Control
Access to the fds in the file descriptor store is generally restricted to the
service code itself. Pushing fds into or removing fds from the fdstore is
@@ -160,7 +160,7 @@ By default only the main service process hence can push/remove fds, but by
setting `NotifyAccess=all` this may be relaxed to allow arbitrary service
child processes to do the same.
# Soft Reboot
## Soft Reboot
The fdstore is particularly interesting in [soft
reboot](https://www.freedesktop.org/software/systemd/man/systemd-soft-reboot.service.html)
@@ -181,7 +181,7 @@ continuously).
For further details see [Resource
Pass-Through](https://www.freedesktop.org/software/systemd/man/systemd-soft-reboot.service.html#Resource%20Pass-Through).
# initrd Transitions
## Initrd Transitions
The fdstore may also be used to pass file descriptors for resources from the
initrd context to the main system. Restarting all processes after the
@@ -198,7 +198,7 @@ The soft reboot cycle transition and the initrd→host transition are
semantically very similar, hence similar rules apply, and in both cases it is
recommended to use the fdstore if pinned resources shall be passed over.
# Debugging
## Debugging
The
[`systemd-analyze`](https://www.freedesktop.org/software/systemd/man/systemd-analyze.html#systemd-analyze%20fdstore%20%5BUNIT...%5D)

2
docs/PORTABLE_SERVICES.md
View File

@@ -5,7 +5,7 @@ layout: default
SPDX-License-Identifier: LGPL-2.1-or-later
---
# Portable Services Introduction
# Portable Services
systemd (since version 239) supports a concept of "Portable Services".
"Portable Services" are a delivery method for system services that uses

10
man/crypttab.xml
View File

@@ -556,8 +556,9 @@
<para>Note that VeraCrypt enforces a minimal allowed PIM value depending on the
password strength and the hash algorithm used for key derivation, however
<option>veracrypt-pim=</option> is not checked against these bounds.
<ulink url="https://www.veracrypt.fr/en/Personal%20Iterations%20Multiplier%20%28PIM%29.html">See
documentation</ulink> for more information.</para>
See
<ulink url="https://www.veracrypt.fr/en/Personal%20Iterations%20Multiplier%20%28PIM%29.html">Veracrypt Personal Iterations Multiplier</ulink>
documentation for more information.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
@@ -980,8 +981,9 @@ external /dev/sda3 keyfile:LABEL=keydev keyfile-timeout=10s,cipher=xchac
<itemizedlist>
<listitem><para>We use RSA2048, which is the longest key size current Yubikeys support</para></listitem>
<listitem><para>We use Yubikey key slot 9d, since that's apparently the keyslot to use for decryption purposes,
<ulink url="https://developers.yubico.com/PIV/Introduction/Certificate_slots.html">see
documentation</ulink>.</para></listitem>
see
<ulink url="https://developers.yubico.com/PIV/Introduction/Certificate_slots.html">Yubico PIV certificate slots</ulink>.
</para></listitem>
</itemizedlist>
</example>

2
man/journalctl.xml
View File

@@ -865,7 +865,7 @@
<para><option>--vacuum-time=</option> removes archived journal files older than the specified
timespan. Accepts the usual <literal>s</literal> (default), <literal>m</literal>,
<literal>h</literal>, <literal>days</literal>, <literal>months</literal>, <literal>weeks</literal>
<literal>h</literal>, <literal>days</literal>, <literal>weeks</literal>, <literal>months</literal>,
and <literal>years</literal> suffixes, see
<citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
details.</para>

10
man/machinectl.xml
View File

@@ -413,10 +413,12 @@
<varlistentry>
<term><command>edit</command> <replaceable>NAME|FILE</replaceable></term>
<listitem><para>Edit the settings file of the specified machines. For the format of the settings file, refer to <citerefentry
project='man-pages'><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
If an existing settings file of the given machine can't be found, <command>edit</command> automatically
create a new settings file from scratch under <filename>/etc/</filename></para>
<listitem><para>Edit the settings file of the specified machines. For the format of the settings
file, refer to
<citerefentry project='man-pages'><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
If an existing settings file of the given machine can't be found, <command>edit</command>
automatically create a new settings file from scratch under <filename>/etc/</filename>.
</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
</varlistentry>

59
man/networkctl.xml
View File

@@ -72,7 +72,7 @@
<varlistentry>
<term>missing</term>
<listitem>
<para>the device is missing</para>
<para>The device is missing.</para>
<xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
@@ -80,7 +80,7 @@
<varlistentry>
<term>off</term>
<listitem>
<para>the device is powered down</para>
<para>The device is powered down.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -88,7 +88,7 @@
<varlistentry>
<term>no-carrier</term>
<listitem>
<para>the device is powered up, but it does not yet have a carrier</para>
<para>The device is powered up, but does not yet have a carrier.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -96,7 +96,7 @@
<varlistentry>
<term>dormant</term>
<listitem>
<para>the device has a carrier, but is not yet ready for normal traffic</para>
<para>The device has a carrier, but is not yet ready for normal traffic.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -104,7 +104,8 @@
<varlistentry>
<term>degraded-carrier</term>
<listitem>
<para>one of the bonding or bridge slave network interfaces is in off, no-carrier, or dormant state, and the master interface has no address.</para>
<para>One of the bonding or bridge slave network interfaces is in off, no-carrier, or
dormant state, and the master interface has no address.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
@@ -112,8 +113,8 @@
<varlistentry>
<term>carrier</term>
<listitem>
<para>the link has a carrier, or for bond or bridge master, all bonding or bridge slave
network interfaces are enslaved to the master</para>
<para>The link has carrier, or for bond or bridge master, all bonding or bridge slave
network interfaces are enslaved to the master.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -121,7 +122,7 @@
<varlistentry>
<term>degraded</term>
<listitem>
<para>the link has carrier and addresses valid on the local link configured. For bond or
<para>The link has carrier and addresses valid on the local link configured. For bond or
bridge master this means that not all slave network interfaces have carrier but at least
one does.</para>
@@ -131,7 +132,8 @@
<varlistentry>
<term>enslaved</term>
<listitem>
<para>the link has carrier and is enslaved to bond or bridge master network interface</para>
<para>The link has carrier and is enslaved to bond or bridge master network interface.
</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
@@ -139,7 +141,7 @@
<varlistentry>
<term>routable</term>
<listitem>
<para>the link has carrier and routable address configured. For bond or bridge master it is
<para>The link has carrier and routable address configured. For bond or bridge master it is
not necessary for all slave network interfaces to have carrier, but at least one must.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
@@ -153,7 +155,8 @@
<varlistentry>
<term>pending</term>
<listitem>
<para>udev is still processing the link, we don't yet know if we will manage it</para>
<para><citerefentry><refentrytitle>systemd-udevd</refentrytitle><manvolnum>8</manvolnum></citerefentry>
is still processing the link, we don't yet know if we will manage it.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -161,7 +164,8 @@
<varlistentry>
<term>initialized</term>
<listitem>
<para>udev has processed the link, but we don't yet know if we will manage it</para>
<para><citerefentry><refentrytitle>systemd-udevd</refentrytitle><manvolnum>8</manvolnum></citerefentry>
has processed the link, but we don't yet know if we will manage it.</para>
<xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
@@ -169,7 +173,7 @@
<varlistentry>
<term>configuring</term>
<listitem>
<para>in the process of retrieving configuration or configuring the link</para>
<para>Configuration for the link is being retrieved or the link is being configured.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -177,7 +181,7 @@
<varlistentry>
<term>configured</term>
<listitem>
<para>link configured successfully</para>
<para>Link has been configured successfully.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -185,7 +189,7 @@
<varlistentry>
<term>unmanaged</term>
<listitem>
<para>networkd is not handling the link</para>
<para><command>systemd-networkd</command> is not handling the link.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -193,7 +197,7 @@
<varlistentry>
<term>failed</term>
<listitem>
<para>networkd failed to manage the link</para>
<para><command>systemd-networkd</command> failed to configure the link.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -201,7 +205,7 @@
<varlistentry>
<term>linger</term>
<listitem>
<para>the link is gone, but has not yet been dropped by networkd</para>
<para>The link is gone, but has not yet been dropped by <command>systemd-networkd</command>.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
@@ -246,7 +250,7 @@
<varlistentry>
<term>unknown</term>
<listitem>
<para>all links have unknown online status (i.e. there are no required links)</para>
<para>All links have unknown online status (i.e. there are no required links).</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
@@ -254,7 +258,7 @@
<varlistentry>
<term>offline</term>
<listitem>
<para>all required links are offline</para>
<para>All required links are offline.</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
@@ -262,7 +266,7 @@
<varlistentry>
<term>partial</term>
<listitem>
<para>some, but not all, required links are online</para>
<para>Some, but not all, required links are online.</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
@@ -270,7 +274,7 @@
<varlistentry>
<term>online</term>
<listitem>
<para>all required links are online</para>
<para>All required links are online.</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
@@ -436,7 +440,8 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
the main configuration file. Unless <option>--no-reload</option> is specified,
<command>systemd-networkd</command> will be reloaded after the edit of the
<filename>.network</filename> or <filename>.netdev</filename> files finishes.
The same applies for <filename>.link</filename> files and <command>systemd-udevd</command>.
The same applies for <filename>.link</filename> files and
<citerefentry><refentrytitle>systemd-udevd</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
Note that the changed link settings are not automatically applied after reloading.
To achieve that, trigger uevents for the corresponding interface. Refer to
<citerefentry><refentrytitle>systemd.link</refentrytitle><manvolnum>5</manvolnum></citerefentry>
@@ -514,8 +519,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
</varlistentry>
<varlistentry>
<term><option>--drop-in=</option></term>
<replaceable>NAME</replaceable>
<term><option>--drop-in=</option><replaceable>NAME</replaceable></term>
<listitem>
<para>When used with <command>edit</command>, edit the drop-in file <replaceable>NAME</replaceable>
@@ -529,8 +533,11 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
<term><option>--no-reload</option></term>
<listitem>
<para>When used with <command>edit</command>, <command>systemd-networkd</command>
or <command>systemd-udevd</command> will not be reloaded after the editing finishes.</para>
<para>When used with <command>edit</command>,
<citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
or
<citerefentry><refentrytitle>systemd-udevd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
will not be reloaded after the editing finishes.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>

4
man/os-release.xml
View File

@@ -104,7 +104,7 @@
<para><filename>/usr/lib/extension-release.d/extension-release.<replaceable>IMAGE</replaceable></filename>
plays the same role for extension images as <filename>os-release</filename> for the main system, and
follows the syntax and rules as described in the <ulink
url="https://systemd.io/PORTABLE_SERVICES">Portable Services Documentation</ulink>. The purpose of this
url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink> page. The purpose of this
file is to identify the extension and to allow the operating system to verify that the extension image
matches the base OS. This is typically implemented by checking that the <varname>ID=</varname> options
match, and either <varname>SYSEXT_LEVEL=</varname> exists and matches too, or if it is not present,
@@ -534,7 +534,7 @@
<varlistentry>
<term><varname>PORTABLE_PREFIXES=</varname></term>
<listitem><para>Takes a space-separated list of one or more valid prefix match strings for the
<ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services Documentation</ulink> logic.
<ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink> logic.
This field serves two purposes: it is informational, identifying portable service images as such
(and thus allowing them to be distinguished from other OS images, such as bootable system images).
It is also used when a portable service image is attached: the specified or implied portable

22
man/resolvectl.xml
View File

@@ -77,17 +77,17 @@
[[<replaceable>NAME</replaceable>] <replaceable>TYPE</replaceable>]
<replaceable>DOMAIN</replaceable></term>
<listitem><para>Resolve <ulink url="https://tools.ietf.org/html/rfc6763">DNS-SD</ulink> and <ulink
url="https://tools.ietf.org/html/rfc2782">SRV</ulink> services, depending on the specified list of
parameters. If three parameters are passed the first is assumed to be the DNS-SD service name, the
second the <constant class='dns'>SRV</constant> service type, and the third the domain to search in.
In this case a full DNS-SD style <constant class='dns'>SRV</constant> and <constant
class='dns'>TXT</constant> lookup is executed. If only two parameters are specified, the first is
assumed to be the <constant class='dns'>SRV</constant> service type, and the second the domain to look
in. In this case no <constant class='dns'>TXT</constant> resource record is requested. Finally, if
only one parameter is specified, it is assumed to be a domain name, that is already prefixed with an
<constant class='dns'>SRV</constant> type, and an <constant class='dns'>SRV</constant> lookup is done
(no <constant class='dns'>TXT</constant>).</para>
<listitem><para>Resolve <ulink url="https://tools.ietf.org/html/rfc6763">RFC 6763 DNS-SD</ulink> and
<ulink url="https://tools.ietf.org/html/rfc2782">RFC 2782 SRV</ulink> services, depending on the
specified list of parameters. If three parameters are passed the first is assumed to be the DNS-SD
service name, the second the <constant class='dns'>SRV</constant> service type, and the third the
domain to search in. In this case a full DNS-SD style <constant class='dns'>SRV</constant> and
<constant class='dns'>TXT</constant> lookup is executed. If only two parameters are specified, the
first is assumed to be the <constant class='dns'>SRV</constant> service type, and the second the
domain to look in. In this case no <constant class='dns'>TXT</constant> resource record is requested.
Finally, if only one parameter is specified, it is assumed to be a domain name, that is already
prefixed with an <constant class='dns'>SRV</constant> type, and an <constant
class='dns'>SRV</constant> lookup is done (no <constant class='dns'>TXT</constant>).</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>

22
man/resolved.conf.xml
View File

@@ -363,17 +363,21 @@ DNSStubListenerExtra=udp:[2001:db8:0:f102::13]:9953</programlisting>
</varlistentry>
<varlistentry>
<term>StaleRetentionSec=<replaceable>SECONDS</replaceable></term>
<listitem><para>Takes a duration value, which determines the length of time DNS resource records can be retained
in the cache beyond their Time To Live (TTL). This allows these records to be returned as stale records.
By default, this value is set to zero, meaning that DNS resource records are not stored in the cache after their TTL expires.</para>
<listitem><para>Takes a duration value, which determines the length of time DNS resource records can
be retained in the cache beyond their Time To Live (TTL). This allows these records to be returned as
stale records. By default, this value is set to zero, meaning that DNS resource records are not
stored in the cache after their TTL expires.</para>
<para>This is useful when a DNS server failure occurs or becomes unreachable.
In such cases, systemd-resolved continues to use the stale records to answer DNS queries, particularly when no valid response
can be obtained from the upstream DNS servers. However, this doesn't apply to NXDOMAIN responses, as those are still perfectly valid responses.
This feature enhances resilience against DNS infrastructure failures and outages.</para>
<para>This is useful when a DNS server failure occurs or becomes unreachable. In such cases,
<citerefentry><refentrytitle>systemd-resolved</refentrytitle><manvolnum>8</manvolnum></citerefentry>
continues to use the stale records to answer DNS queries, particularly when no valid response can be
obtained from the upstream DNS servers. However, this doesn't apply to NXDOMAIN responses, as those
are still perfectly valid responses. This feature enhances resilience against DNS infrastructure
failures and outages.</para>
<para>systemd-resolved always attempts to reach the upstream DNS servers first, before providing the client application with any stale data.
If this feature is enabled, cache will not be flushed when changing servers.</para>
<para><command>systemd-resolved</command> always attempts to reach the upstream DNS servers first,
before providing the client application with any stale data. If this feature is enabled, cache will
not be flushed when changing servers.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>

2
man/sd-id128.xml
View File

@@ -190,7 +190,7 @@ int main(int argc, char **argv) {
are similar to
<constant>SD_ID128_FORMAT_STR</constant> and <function>SD_ID128_MAKE_STR()</function>,
but include separating hyphens to conform to the
"<ulink url="https://en.wikipedia.org/wiki/Universally_unique_identifier#Format">canonical representation</ulink>".
"<ulink url="https://en.wikipedia.org/wiki/Universally_unique_identifier#Format">UUID canonical representation</ulink>".
They format the string based on <ulink
url="https://tools.ietf.org/html/rfc4122">RFC4122</ulink> Variant 1 rules, i.e. converting from Big
Endian byte order. This matches behaviour of most other Linux userspace infrastructure. It's probably

2
man/sd_bus_error.xml
View File

@@ -163,7 +163,7 @@
<listitem><para>The <structfield>name</structfield> field contains a short identifier of an error. It
should follow the rules for error names described in the D-Bus specification, subsection <ulink
url="https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names">Valid
Names</ulink>. A number of common, standardized error names are described in
D-Bus Names</ulink>. A number of common, standardized error names are described in
<citerefentry><refentrytitle>sd-bus-errors</refentrytitle><manvolnum>3</manvolnum></citerefentry>, but
additional domain-specific errors may be defined by applications.</para></listitem>

2
man/sd_bus_message_append_array.xml
View File

@@ -80,7 +80,7 @@
<literal>t</literal>, <literal>d</literal> (but not
<literal>b</literal>), as defined by the <ulink
url="https://dbus.freedesktop.org/doc/dbus-specification.html#basic-types">Basic
Types</ulink> section of the D-Bus specification, and listed in
D-Bus Types</ulink> section of the D-Bus specification, and listed in
<citerefentry><refentrytitle>sd_bus_message_append_basic</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
Pointer <parameter>p</parameter> must point to an array of size
<parameter>size</parameter> bytes containing items of the

2
man/sd_bus_set_description.xml
View File

@@ -121,7 +121,7 @@
i.e. lack of authentication, of the bus peer. This function must be called before the bus is
started. See the
<ulink url="view-source:https://dbus.freedesktop.org/doc/dbus-specification.html#auth-mechanisms">
Authentication Mechanisms</ulink> section of the D-Bus specification for details.</para>
D-Bus Authentication Mechanisms</ulink> section of the D-Bus specification for details.</para>
<para><function>sd_bus_is_anonymous()</function> returns true if the bus connection allows
anonymous authentication (in the sense described in previous paragraph).</para>

6
man/systemctl.xml
View File

@@ -2740,11 +2740,11 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
</varlistentry>
<varlistentry>
<term><option>--drop-in=</option></term>
<term><option>--drop-in=</option><replaceable>NAME</replaceable></term>
<listitem>
<para>When used with <command>edit</command>, use the given drop-in file name instead of
<filename>override.conf</filename>.</para>
<para>When used with <command>edit</command>, use <replaceable>NAME</replaceable> as the drop-in
file name instead of <filename>override.conf</filename>.</para>
<xi:include href="version-info.xml" xpointer="v253"/>
</listitem>

2
man/systemd-analyze.xml
View File

@@ -863,7 +863,7 @@ stored sock 0:8 4213190 - socket:[4213190] ro
<citerefentry><refentrytitle>systemd.image-policy</refentrytitle><manvolnum>7</manvolnum></citerefentry>. The
policy is normalized and simplified. For each currently defined partition identifier (as per the <ulink
url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable
Partitions Specification</ulink> the effect of the image policy string is shown in tabular form.</para>
Partitions Specification</ulink>) the effect of the image policy string is shown in tabular form.</para>
<example>
<title>Example Output</title>

15
man/systemd-battery-check.service.xml
View File

@@ -18,7 +18,7 @@
<refnamediv>
<refname>systemd-battery-check.service</refname>
<refname>systemd-battery-check</refname>
<refpurpose>Check battery level whether there's enough charge, and power off if not.</refpurpose>
<refpurpose>Check battery level whether there's enough charge, and power off if not</refpurpose>
</refnamediv>
<refsynopsisdiv>
@@ -32,14 +32,11 @@
<refsect1>
<title>Description</title>
<para>
<filename>systemd-battery-check.service</filename> is used to check the battery level during the early
boot stage to determine whether there's sufficient battery power to carry on with the booting process.
</para>
<para>
<command>systemd-battery-check</command> returns success if the device is connected to an AC power
source or if the battery charge is greater than 5%. It returns failure otherwise.
</para>
<para>This service checks the presence of an external power supply and the battery level during the early
boot stage to determine whether there is sufficient power to carry on with the booting process.</para>
<para><command>systemd-battery-check</command> returns success if the device is connected to an AC power
source or if the battery charge is greater than 5%. It returns failure otherwise.</para>
</refsect1>
<refsect1>

4
man/systemd-firstboot.xml
View File

@@ -293,8 +293,8 @@
<term><option>--force</option></term>
<listitem><para>Write configuration even if the relevant files already exist. Without this option,
<filename>systemd-firstboot</filename> doesn't modify or replace existing files. Note that when
configuring the root account, even with this option, <filename>systemd-firstboot</filename> only
<command>systemd-firstboot</command> doesn't modify or replace existing files. Note that when
configuring the root account, even with this option, <command>systemd-firstboot</command> only
modifies the entry of the <literal>root</literal> user, leaving other entries in
<filename>/etc/passwd</filename> and <filename>/etc/shadow</filename> intact.</para>

Some files were not shown because too many files have changed in this diff Show More