SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

man: fix typos and grammar in various man pages

Browse Source
This commit is contained in:
Yu Watanabe
2026-09-17 02:25:12 +09:00
parent b1cb951a6f
commit 15bd45d113
28 changed files with 61 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/capsule@.service.xml
+1 -1
View File
@@ -77,7 +77,7 @@
for example with the <option>--what=all</option> switch.</para>
<para>The <filename>capsule@.service</filename> unit invokes a <command>systemd --user</command>
service manager process. This means unit files are looked for according to the sames rules as for regular user
service manager process. This means unit files are looked for according to the same rules as for regular user
service managers, for example in
<filename>/var/lib/capsules/<replaceable>NAME</replaceable>/.config/systemd/user/</filename>.</para>
man/dnssec-trust-anchors.d.xml
+1 -1
View File
@@ -156,7 +156,7 @@ stag
set of well-known private DNS zone domains is used as negative
trust anchors.</para>
<para>It is also possibly to define per-interface negative trust
<para>It is also possible to define per-interface negative trust
anchors using the <varname>DNSSECNegativeTrustAnchors=</varname>
setting in
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>
man/org.freedesktop.systemd1.xml
+9 -9
View File
@@ -33,7 +33,7 @@
for each unit and for each queued job. The unit objects implement a generic
<interfacename>Unit</interfacename> interface as well as a type-specific interface. For example, service units
implement both <interfacename>org.freedesktop.systemd1.Unit</interfacename> and
<interfacename>org.freedesktop.system1.Service</interfacename>. The manager object can list
<interfacename>org.freedesktop.systemd1.Service</interfacename>. The manager object can list
unit and job objects or directly convert a unit name or job identifier to a bus path of the corresponding
D-Bus object.</para>
@@ -1518,7 +1518,7 @@ node /org/freedesktop/systemd1 {
<orderedlist>
<listitem><para>Send a D-Bus message that will turn off status messages.</para></listitem>
<listitem><para>Block until a reply to that message is received.</para></listitem>
<listitem><para>Print multiples lines without being interrupted by status messages.</para></listitem>
<listitem><para>Print multiple lines without being interrupted by status messages.</para></listitem>
<listitem><para>Send a D-Bus message that will reset <varname>ShowStatus</varname> back to its
original value.</para></listitem>
</orderedlist>
@@ -2086,7 +2086,7 @@ node /org/freedesktop/systemd1 {
operations are allowed through the polkit privilege system. Operations which modify unit state
(<function>StartUnit()</function>, <function>StopUnit()</function>, <function>KillUnit()</function>,
<function>KillUnitSubgroup()</function>, <function>QueueSignalUnit()</function>,
<function>RestartUnit()</function> and similar, <function>SetProperty()</function>) require
<function>RestartUnit()</function> and similar, <function>SetUnitProperties()</function>) require
<interfacename>org.freedesktop.systemd1.manage-units</interfacename>. Operations which modify unit file
enablement state (<function>EnableUnitFiles()</function>, <function>DisableUnitFiles()</function>,
<function>EnableUnitFilesWithFlags()</function>, <function>DisableUnitFilesWithFlags()</function>,
@@ -5209,12 +5209,12 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
for more details on how to retrieve these file descriptors. Unlike the <varname>ExtraFileDescriptors</varname>
input property, <varname>ExtraFileDescriptorNames</varname> only contains names and not the file descriptors.</para>
<para><varname>ManagedOOMMemoryPressureDurationUSec</varname> implement the destination parameter of the
<para><varname>ManagedOOMMemoryPressureDurationUSec</varname> implements the destination parameter of the
unit file setting <varname>ManagedOOMMemoryPressureDurationSec=</varname> listed in
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Note the time unit is expressed in <literal>μs</literal>.</para>
<para><varname>ProtectControlGroupsEx</varname> implement the destination parameter of the
<para><varname>ProtectControlGroupsEx</varname> implements the destination parameter of the
unit file setting <varname>ProtectControlGroups=</varname> listed in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Unlike boolean <varname>ProtectControlGroups</varname>, <varname>ProtectControlGroupsEx</varname>
@@ -5225,7 +5225,7 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Note <varname>PrivatePIDs</varname> is a string type to allow adding more values in the future.</para>
<para><varname>ProtectHostnameEx</varname> implement the destination parameter of the
<para><varname>ProtectHostnameEx</varname> implements the destination parameter of the
unit file setting <varname>ProtectHostname=</varname> listed in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Unlike boolean <varname>ProtectHostname</varname>, <varname>ProtectHostnameEx</varname> is a pair of
@@ -12047,7 +12047,7 @@ node /org/freedesktop/systemd1/unit/system_2eslice {
<para>Most properties correspond directly with the matching settings in slice unit files.</para>
<para><varname>ManagedOOMMemoryPressureDurationUSec</varname> implement the destination parameter of the
<para><varname>ManagedOOMMemoryPressureDurationUSec</varname> implements the destination parameter of the
unit file setting <varname>ManagedOOMMemoryPressureDurationSec=</varname> listed in
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Note the time unit is expressed in <literal>μs</literal>.</para>
@@ -12726,10 +12726,10 @@ node /org/freedesktop/systemd1/unit/session_2d1_2escope {
<para><varname>Controller</varname> contains the bus name (unique or well-known) that is notified when
the scope unit is to be shut down via a <function>RequestStop()</function> signal (see below). This is
set when the scope is created. If not set, the scope's processes will terminated with
set when the scope is created. If not set, the scope's processes will be terminated with
<constant>SIGTERM</constant> directly.</para>
<para><varname>ManagedOOMMemoryPressureDurationUSec</varname> implement the destination parameter of the
<para><varname>ManagedOOMMemoryPressureDurationUSec</varname> implements the destination parameter of the
unit file setting <varname>ManagedOOMMemoryPressureDurationSec=</varname> listed in
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Note the time unit is expressed in <literal>μs</literal>.</para>
man/org.freedesktop.sysupdate1.xml
+1 -1
View File
@@ -96,7 +96,7 @@ node /org/freedesktop/sysupdate1 {
<para>The <function>JobRemoved()</function> signal is sent each time a job finishes,
is canceled or fails. It also carries the job ID and object path, followed by a numeric status
code. If the status is zero, the job has succeed. A positive status should be treated as an
code. If the status is zero, the job has succeeded. A positive status should be treated as an
exit code (i.e. <literal>EXIT_FAILURE</literal>), and a negative status should be treated as a
negative errno-style error code (i.e. <literal>-EINVAL</literal>).</para>
</refsect2>
man/portablectl.xml
+1 -1
View File
@@ -122,7 +122,7 @@
<para>By default, all unit files whose names start with a prefix generated from the image's file name are copied
out. Specifically, the prefix is determined from the image file name with any suffix such as
<filename>.raw</filename> removed, truncated at the first occurrence of an underscore character
(<literal>_</literal>), if there is one. The underscore logic is supposed to be used to versioning so that the
(<literal>_</literal>), if there is one. The underscore logic is supposed to be used for versioning so that
an image file <filename>foobar_47.11.raw</filename> will result in a unit file matching prefix of
<filename>foobar</filename>. This prefix is then compared with all unit files names contained in the image in
the usual directories, but only unit file names where the prefix is followed by <literal>-</literal>,
man/repart.d.xml
+1 -1
View File
@@ -249,7 +249,7 @@
<listitem><para>The textual label to assign to the partition if none is assigned yet. Note that this
setting is not used for matching. It is also not used when a label is already set for an existing
partition. It is thus only used when a partition is newly created or when an existing one had a no
partition. It is thus only used when a partition is newly created or when an existing one had no
label set (that is: an empty label). If not specified, a label derived from the partition type is
automatically used. Simple specifier expansion is supported, see below.</para>
man/sd_bus_error.xml
+1 -1
View File
@@ -238,7 +238,7 @@
due to lack of memory, in which case an <constant>SD_BUS_ERROR_NO_MEMORY</constant> error is set instead,
and <constant>-ENOMEM</constant> is returned.</para>
<para><function>sd_bus_error_set_errnof()</function> and <function>sd_bus_error_set_errnof()</function>
<para><function>sd_bus_error_set_errnof()</function> and <function>sd_bus_error_set_errnofv()</function>
are similar to <function>sd_bus_error_set_errno()</function>, but in addition to
<parameter>error</parameter>, take a <citerefentry
project='man-pages'><refentrytitle>printf</refentrytitle><manvolnum>3</manvolnum></citerefentry> format
man/sd_bus_list_names.xml
+2 -2
View File
@@ -44,8 +44,8 @@
org.freedesktop.DBus.ListNames</ulink> to retrieve the list of currently-owned names on the bus. If
<parameter>acquired</parameter> is not <constant>NULL</constant>, the function calls
<ulink url="https://dbus.freedesktop.org/doc/dbus-specification.html#bus-messages-list-activatable-names">
org.freedesktop.DBus.ListActivableNames</ulink> to retrieve the list of all names on the bus that can be
activated. Note that ownership of the arrays returned by <function>sd_bus_list_names()</function> in
org.freedesktop.DBus.ListActivatableNames</ulink> to retrieve the list of all names on the bus that can
be activated. Note that ownership of the arrays returned by <function>sd_bus_list_names()</function> in
<parameter>acquired</parameter> and <parameter>activatable</parameter> is transferred to the caller and
hence, the caller is responsible for freeing these arrays and their contents.</para>
</refsect1>
man/sd_bus_message_get_cookie.xml
+1 -1
View File
@@ -19,7 +19,7 @@
<refnamediv>
<refname>sd_bus_message_get_cookie</refname>
<refname>sd_bus_message_get_reply_cookie</refname>
<refpurpose>Returns the transaction cookie of a message</refpurpose>
<refpurpose>Return the transaction cookie of a message</refpurpose>
</refnamediv>
<refsynopsisdiv>
man/sd_bus_set_watch_bind.xml
+9 -8
View File
@@ -44,14 +44,15 @@
<refsect1>
<title>Description</title>
<para><function>sd_bus_set_watch_bind()</function> may be used to enable or disable client-side watching of server
socket binding for a bus connection object. If the <parameter>b</parameter> is true, the feature is enabled,
otherwise disabled (which is the default). When enabled, and the selected bus address refers to an
<filename>AF_UNIX</filename> socket in the file system which does not exist while the connection attempt is made an
<citerefentry project='man-pages'><refentrytitle>inotify</refentrytitle><manvolnum>7</manvolnum></citerefentry> watch is installed on
it, waiting for the socket to appear. As soon as the socket appears the connection is made. This functionality is
useful in particular in early-boot programs that need to run before the system bus is available, but want to
connect to it the instant it may be connected to.</para>
<para><function>sd_bus_set_watch_bind()</function> may be used to enable or disable client-side watching
of server socket binding for a bus connection object. If <parameter>b</parameter> is true, the feature is
enabled, otherwise disabled (which is the default). When enabled, and the selected bus address refers to
an <filename>AF_UNIX</filename> socket in the file system which does not exist while the connection
attempt is made, an
<citerefentry project='man-pages'><refentrytitle>inotify</refentrytitle><manvolnum>7</manvolnum></citerefentry>
watch is installed on it, waiting for the socket to appear. As soon as the socket appears the connection
is made. This functionality is useful in particular in early-boot programs that need to run before the
system bus is available, but want to connect to it the instant it may be connected to.</para>
<para><function>sd_bus_get_watch_bind()</function> may be used to query the current setting of this feature. It
returns zero when the feature is disabled, and positive if enabled.</para>
man/sd_device_enumerator_add_match_parent.xml
+1 -1
View File
@@ -144,7 +144,7 @@
<para>The <function>sd_device_enumerator_add_nomatch_sysname()</function> function adds a filter
so that devices whose sysname equals to <parameter>sysname</parameter> are excluded from the
enumeration. This is useful for excluding specific devices from the enumeration process.
When called multiple times, features are ANDed.</para>
When called multiple times, filters are ANDed.</para>
<para>The <function>sd_device_enumerator_add_match_tag()</function> function adds a filter so that
only devices tagged with <parameter>tag</parameter> are enumerated. When called multiple times,
man/sd_event_source_unref.xml
+5 -5
View File
@@ -78,11 +78,11 @@
<para><function>sd_event_source_ref()</function> may be used to increase by one the internal reference
counter of the event source object specified as <parameter>source</parameter>.</para>
<para><function>sd_event_source_unref()</function>,
<function>sd_bus_creds_unrefp()</function> and
<function>sd_bus_creds_ref()</function> execute no operation if
the passed event source object is
<constant>NULL</constant>.</para>
<para><function>sd_event_source_ref()</function> and
<function>sd_event_source_unref()</function> execute no operation if the passed event source
object is <constant>NULL</constant>. <function>sd_event_source_unrefp()</function> will first
dereference its argument, which must not be <constant>NULL</constant>, and will execute no
operation if <emphasis>that</emphasis> is <constant>NULL</constant>.</para>
<para>Note that event source objects stay alive and may be dispatched as long as they have a reference
counter greater than zero. In order to drop a reference of an event source and make sure the associated
man/sd_journal_print.xml
+1 -1
View File
@@ -163,7 +163,7 @@
<function>sd_journal_print()</function> and <function>sd_journal_send()</function> described above, which are based
on format strings, and do strip trailing whitespace.</para>
<para><function>sd_journal_perror()</function> is a similar to
<para><function>sd_journal_perror()</function> is similar to
<citerefentry project='die-net'><refentrytitle>perror</refentrytitle><manvolnum>3</manvolnum></citerefentry>
and writes a message to the journal that consists of the passed
string, suffixed with ": " and a human-readable representation of
man/sd_journal_query_unique.xml
+2 -2
View File
@@ -117,8 +117,8 @@
<para><function>sd_journal_query_unique()</function> returns 0 on success or a negative errno-style error
code. <function>sd_journal_enumerate_unique()</function> and
<function>sd_journal_query_available_unique()</function> return a positive integer if the next field data
has been read, 0 when no more fields remain, or a negative errno-style error code.
<function>sd_journal_enumerate_available_unique()</function> return a positive integer if the next field
data has been read, 0 when no more fields remain, or a negative errno-style error code.
<function>sd_journal_restart_unique()</function> does not return anything.</para>
<refsect2>
man/sysctl.d.xml
+1 -1
View File
@@ -155,7 +155,7 @@ net.bridge.bridge-nf-call-arptables = 0
<para>This method forces the module to be always loaded. Please
note that, unless the <filename>br_netfilter</filename> module is
loaded, bridged packets will not be filtered with Netfilter
loaded, bridged packets will not be filtered by Netfilter
(starting with kernel 3.18), so simply not loading the module is
sufficient to avoid filtering.</para>
</example>
man/systemctl.xml
+5 -6
View File
@@ -740,8 +740,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
(e.g.: with <option>RootImage=</option>, <option>PrivateMounts=</option>, etc.). This command
supports bind-mounting directories, regular files, device nodes, <constant>AF_UNIX</constant>
socket nodes, as well as FIFOs. The bind mount is ephemeral, and it is undone as soon as the
current unit process exists. Note that the namespace mentioned here, where the bind mount will be
added to, is the one where the main service process runs. Other processes (those exececuted by
current unit process exits. Note that the namespace mentioned here, where the bind mount will be
added to, is the one where the main service process runs. Other processes (those executed by
<option>ExecReload=</option>, <option>ExecStartPre=</option>, etc.) run in distinct namespaces.
</para>
@@ -767,15 +767,14 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<option>RootImage=</option>/<option>RootDirectory=</option>). The following argument, if any, is
interpreted as a colon-separated tuple of partition name and comma-separated list of mount options
for that partition. The format is the same as the service <option>MountImages=</option>
setting. When combined with the <option>--read-only</option> switch, a ready-only mount is
setting. When combined with the <option>--read-only</option> switch, a read-only mount is
created. When combined with the <option>--mkdir</option> switch, the destination path is first
created before the mount is applied.</para>
<para>Note that this option is currently only supported for units that run within a mount namespace
(i.e. with <option>RootImage=</option>, <option>PrivateMounts=</option>, etc.). Note that the
namespace mentioned here where the image mount will be added to, is the one where the main service
process runs. Note that the namespace mentioned here, where the bind mount will be
added to, is the one where the main service process runs. Other processes (those exececuted by
namespace mentioned here, where the image mount will be added to, is the one where the main
service process runs. Other processes (those executed by
<option>ExecReload=</option>, <option>ExecStartPre=</option>, etc.) run in distinct namespaces.
</para>
man/systemd-boot-random-seed.service.xml
+1 -1
View File
@@ -82,7 +82,7 @@
the boot loader random seed with a new value derived from the kernel entropy pool.</para></listitem>
</orderedlist>
<para>This logic should ensure that the kernel's entropy pool is seeded during earliest bool already, if
<para>This logic should ensure that the kernel's entropy pool is seeded during earliest boot already, if
possible, but the highest quality entropy is propagated back to both on-disk seeds.</para>
</refsect1>
man/systemd-bsod.service.xml
+1 -1
View File
@@ -19,7 +19,7 @@
<refnamediv>
<refname>systemd-bsod.service</refname>
<refname>systemd-bsod</refname>
<refpurpose>Displays boot-time emergency log message in full screen</refpurpose>
<refpurpose>Display boot-time emergency log message in full screen</refpurpose>
</refnamediv>
<refsynopsisdiv>
man/systemd-factory-reset.xml
+1 -1
View File
@@ -37,7 +37,7 @@
<title>Description</title>
<para><filename>systemd-factory-reset</filename> is a tool that can query the current factory reset
state, request factory request operations or complete them.</para>
state, request factory reset operations or complete them.</para>
<para>Some of the functionality is also available via the
<filename>/run/systemd/io.systemd.FactoryReset</filename> Varlink service (implemented via the
man/systemd-fsck@.service.xml
+2 -2
View File
@@ -124,8 +124,8 @@
<term><varname>fsck.repair</varname></term>
<listitem>
<para>The contents of the credentials are parsed as same as the kernel command line options with
the same name. See above for more details.</para>
<para>The contents of the credentials are parsed in the same way as the kernel command line options
of the same name. See above for more details.</para>
<xi:include href="version-info.xml" xpointer="v258"/>
</listitem>
man/systemd-getty-generator.xml
+1 -1
View File
@@ -82,7 +82,7 @@
active kernel consoles will be enabled. This option will be ignored when the system is running in a
container.</para>
<para>When <literal>builtins</literal> is specified, <filename>serial-getty@.service</filename> for
<para>When <literal>builtin</literal> is specified, <filename>serial-getty@.service</filename> for
available virtualizer consoles will be enabled. This option will be ignored when the system is
running in a container.</para>
man/systemd-journal-upload.service.xml
+4 -4
View File
@@ -45,10 +45,10 @@
Unless limited by one of the options specified below, all journal entries accessible to the user
the program is running as will be uploaded, and then the program will wait and send new entries
as they become available.</para>
<para><command>systemd-journal-upload</command> transfers the raw content of journal file and
uses HTTP as a transport protocol.</para>
<para><command>systemd-journal-upload</command> transfers the raw content of journal files and
uses HTTP as a transport protocol.</para>
<para><filename>systemd-journal-upload.service</filename> is a system service that uses
<command>systemd-journal-upload</command> to upload journal entries to a server. It uses the
configuration in
man/systemd-quotacheck@.service.xml
+2 -2
View File
@@ -75,8 +75,8 @@
<term><varname>quotacheck.mode</varname></term>
<listitem>
<para>The contents of the credential is parsed as same as the kernel command line option with the
same name. See above for more details.</para>
<para>The contents of the credential are parsed in the same way as the kernel command line option
of the same name. See above for more details.</para>
<xi:include href="version-info.xml" xpointer="v258"/>
</listitem>
man/systemd-random-seed.service.xml
+1 -1
View File
@@ -75,7 +75,7 @@
entropy when loading the random seed. With this option this behaviour may be changed: it either takes
a boolean parameter or the special string <literal>force</literal>. Defaults to false, in which case
no entropy is credited. If true, entropy is credited if the random seed file and system state pass
various superficial concisistency checks. If set to <literal>force</literal> entropy is credited,
various superficial consistency checks. If set to <literal>force</literal> entropy is credited,
regardless of these checks, as long as the random seed file exists.</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
man/systemd-report-sign-tpm2@.service.xml
+1 -1
View File
@@ -63,7 +63,7 @@
<para>The report additionally includes the measurement event log, and the public area of the signing key.
The public area is provided as a JSON encoded <constant>TPMT_PUBLIC</constant> structure, and in PEM
encooded form.</para>
encoded form.</para>
<para>The preceding components are all executed under the audit session, and the report is only generated
if that session remains exclusive throughout. Because the audit session attestation records whether the
man/systemd.netdev.xml
+3 -2
View File
@@ -1268,9 +1268,10 @@ Ports=eth2</programlisting>
<varlistentry>
<term><varname>Layer2SpecificHeader=</varname></term>
<listitem>
<para>Specifies layer2specific header type of the session. One of <literal>none</literal> or <literal>default</literal>. Defaults to <literal>default</literal>.</para>
<para>Specifies the layer 2 specific header type of the session. One of <literal>none</literal> or
<literal>default</literal>. Defaults to <literal>default</literal>.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
</variablelist>
man/sysusers.d.xml
+1 -1
View File
@@ -251,7 +251,7 @@ r - 500-900
<para>Only applies to lines of type <varname>u</varname> and should otherwise
be left unset (or <literal>-</literal>). It is recommended to omit this, unless
a shell different <filename>/usr/sbin/nologin</filename> must be used.</para>
a shell different from <filename>/usr/sbin/nologin</filename> must be used.</para>
</refsect2>
</refsect1>
man/ukify.xml
+1 -1
View File
@@ -53,7 +53,7 @@
a boot loader. When used with <ulink url="https://www.qemu.org/docs/master/">qemu</ulink>, a UKI can also
be executed through "direct kernel boot", see example below.</para>
<para><command>ukify</command> can also be used generate other types of UKI-like images, in particular
<para><command>ukify</command> can also be used to generate other types of UKI-like images, in particular
extensions. See the description of the <command>build</command> verb below. <command>ukify</command> can
also generate certificates and keys for SecureBoot and PCR signing, see the description of the
<command>genkey</command> verb below. <command>ukify</command> can also print detailed information about