mirror of
https://github.com/Dasharo/systemd.git
synced 2026-03-06 15:02:31 -08:00
treewide: Correct typos and spell plural of bus consistent
This commit is contained in:
committed by
Daniel Mack
parent
4dda4e637e
commit
ff9b60f38b
@@ -58,7 +58,7 @@
|
||||
associated key-value pairs. Every record in the hwdb starts with one or
|
||||
more match string, specifying a shell glob to compare the database
|
||||
lookup string against. Multiple match lines are specified in additional
|
||||
consecutive lines. Every match line is compared indivdually, they are
|
||||
consecutive lines. Every match line is compared individually, they are
|
||||
combined by OR. Every match line must start at the first character of
|
||||
the line.</para>
|
||||
|
||||
|
||||
@@ -90,7 +90,7 @@
|
||||
requires a writable <filename>/etc</filename> file system and is
|
||||
fragile because the file might be edited by the administrator at
|
||||
the same time. With <command>nss-myhostname</command> enabled
|
||||
changing <filename>/etc/hosts</filename> is unncessary, and on
|
||||
changing <filename>/etc/hosts</filename> is unnecessary, and on
|
||||
many systems the file becomes entirely optional.</para>
|
||||
|
||||
<para>To activate the NSS modules, <literal>myhostname</literal>
|
||||
|
||||
@@ -453,7 +453,7 @@
|
||||
|
||||
<para>All functions that take a <parameter>char***</parameter>
|
||||
parameter will store the answer there as an address of a an array
|
||||
of strings. Each invidividual string is NUL-terminated, and the
|
||||
of strings. Each individual string is NUL-terminated, and the
|
||||
array is NULL-terminated as a whole. It will be valid as long as
|
||||
<parameter>c</parameter> remains valid, and should not be freed or
|
||||
modified by the caller.</para>
|
||||
|
||||
@@ -143,7 +143,7 @@
|
||||
recommended to use <function>sd_bus_default()</function>,
|
||||
<function>sd_bus_default_user()</function>,
|
||||
<function>sd_bus_default_system()</function> to connect to the
|
||||
user or system busses.</para>
|
||||
user or system buses.</para>
|
||||
|
||||
<para>If the <varname>$DBUS_SESSION_BUS_ADDRESS</varname> environment
|
||||
variable is set
|
||||
|
||||
@@ -87,7 +87,7 @@
|
||||
Arguments corresponding to this nested sequence follow the same
|
||||
rules as if they were not nested.</para>
|
||||
|
||||
<para>A variant is denoted by <literal>v</literal>. Correspoding
|
||||
<para>A variant is denoted by <literal>v</literal>. Corresponding
|
||||
arguments must include a format string denoting a complete type,
|
||||
and following that, arguments corresponding to the specified type.
|
||||
</para>
|
||||
|
||||
@@ -94,7 +94,7 @@
|
||||
a global, monotonically increasing sequence number to all messages
|
||||
transmitted on the local system, at the time the message was sent.
|
||||
This sequence number is useful for determining message send order,
|
||||
even across different busses of the local system. The sequence
|
||||
even across different buses of the local system. The sequence
|
||||
number combined with the boot ID of the system (as returned by
|
||||
<citerefentry><refentrytitle>sd_id128_get_boot</refentrytitle><manvolnum>3</manvolnum></citerefentry>)
|
||||
is a suitable globally unique identifier for bus messages.</para>
|
||||
|
||||
@@ -95,7 +95,7 @@
|
||||
events or a timeout. If any events are ready to be processed, it
|
||||
returns a positive value, and the events should be processed with
|
||||
<function>sd_event_dispatch</function>. Otherwise, the loop is
|
||||
back in the inital state and <function>sd_event_prepare</function>
|
||||
back in the initial state and <function>sd_event_prepare</function>
|
||||
should be called again.</para>
|
||||
|
||||
<programlisting>
|
||||
|
||||
@@ -154,7 +154,7 @@
|
||||
<command>list-dependencies</command>, i.e. follow
|
||||
dependencies of type <varname>WantedBy=</varname>,
|
||||
<varname>RequiredBy=</varname>,
|
||||
<varname>RequiredByOverrridable=</varname>,
|
||||
<varname>RequiredByOverridable=</varname>,
|
||||
<varname>PartOf=</varname>, <varname>BoundBy=</varname>,
|
||||
instead of <varname>Wants=</varname> and similar.
|
||||
</para>
|
||||
|
||||
@@ -66,7 +66,7 @@
|
||||
of the daemon per connection (inetd-style).
|
||||
</para>
|
||||
|
||||
<para>The daemon to launch and its options should be specifed
|
||||
<para>The daemon to launch and its options should be specified
|
||||
after options intended for <command>systemd-activate</command>.
|
||||
</para>
|
||||
|
||||
@@ -76,7 +76,7 @@
|
||||
inherited, and sockets will be passed through file descriptors 3
|
||||
and higher. Sockets passed through <varname>$LISTEN_FDS</varname>
|
||||
to <command>systemd-activate</command> will be passed through to
|
||||
the dameon, in the original positions. Other sockets specified
|
||||
the daemon, in the original positions. Other sockets specified
|
||||
with <option>--listen</option> will use consecutive descriptors.
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
@@ -64,7 +64,7 @@
|
||||
<filename>/usr/lib/sysctl.d/50-coredump.conf</filename> which
|
||||
configures <varname>kernel.core_pattern</varname> to invoke
|
||||
<command>systemd-coredump</command>. This file may be masked or
|
||||
overriden to use a different setting following normal
|
||||
overridden to use a different setting following normal
|
||||
<citerefentry><refentrytitle>sysctl.d</refentrytitle><manvolnum>5</manvolnum></citerefentry> rules.</para>
|
||||
|
||||
<para>The behaviour of a specific program upon reception of a
|
||||
|
||||
@@ -69,7 +69,7 @@
|
||||
certain configuration files can have <literal>.d</literal>
|
||||
directories which contain "drop-in" files with configuration
|
||||
snippets which augment the main configuration file. "Drop-in"
|
||||
files can be overriden in the same way by placing files with the
|
||||
files can be overridden in the same way by placing files with the
|
||||
same name in a directory of higher priority (except that in case
|
||||
of "drop-in" files, both the "drop-in" file name and the name of
|
||||
the containing directory, which corresponds to the name of the
|
||||
|
||||
@@ -156,7 +156,7 @@
|
||||
<listitem><para>Takes the <filename>/usr</filename> filesystem
|
||||
mount options to use. If <varname>mount.usr=</varname> or
|
||||
<varname>mount.usrfstype=</varname> is set, then
|
||||
<varname>mount.usrflages=</varname> will default to the value
|
||||
<varname>mount.usrflags=</varname> will default to the value
|
||||
set in <varname>rootflags=</varname>.</para>
|
||||
|
||||
<para>Otherwise this value will be read from the
|
||||
|
||||
@@ -156,7 +156,7 @@
|
||||
<varname>$LISTEN_FDS</varname>/<varname>$LISTEN_PID</varname>.
|
||||
In the second case, an HTTP or HTTPS server will be spawned on
|
||||
this port, respectively for <option>--listen-http</option> and
|
||||
<option>--listen-https</option>. Currenntly, only POST requests
|
||||
<option>--listen-https</option>. Currently, only POST requests
|
||||
to <filename>/upload</filename> with <literal>Content-Type:
|
||||
application/vnd.fdo.journal</literal> are supported.</para>
|
||||
</listitem>
|
||||
|
||||
@@ -141,7 +141,7 @@
|
||||
<replaceable>COMMAND</replaceable> specifies the program to launch
|
||||
in the container, and the remaining arguments are used as
|
||||
arguments for this program. If <option>-b</option> is not used and
|
||||
no arguments are specifed, a shell is launched in the
|
||||
no arguments are specified, a shell is launched in the
|
||||
container.</para>
|
||||
|
||||
<para>The following options are understood:</para>
|
||||
@@ -727,7 +727,7 @@
|
||||
<programlisting># pacstrap -c -d ~/arch-tree/ base
|
||||
# systemd-nspawn -bD ~/arch-tree/</programlisting>
|
||||
|
||||
<para>This installs a mimimal Arch Linux distribution into the
|
||||
<para>This installs a minimal Arch Linux distribution into the
|
||||
directory <filename>~/arch-tree/</filename> and then boots an OS
|
||||
in a namespace container in it.</para>
|
||||
</example>
|
||||
|
||||
@@ -140,7 +140,7 @@
|
||||
<listitem>
|
||||
<para><parameter>late-dir</parameter></para>
|
||||
<para>argv[3] may be used to extend the unit file tree without
|
||||
overridding any other unit files. Any native configuration
|
||||
overriding any other unit files. Any native configuration
|
||||
files supplied by the vendor or user/administrator take
|
||||
precedence over the generated ones placed in this directory.
|
||||
</para>
|
||||
|
||||
@@ -390,7 +390,7 @@
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>Priviledged programs (currently UID 0) may attach
|
||||
<para>Privileged programs (currently UID 0) may attach
|
||||
<varname>OBJECT_PID=</varname> to a message. This will instruct
|
||||
<command>systemd-journald</command> to attach additional fields on
|
||||
behalf of the caller:</para>
|
||||
|
||||
@@ -106,7 +106,7 @@
|
||||
</para>
|
||||
|
||||
<para>Some file systems have special semantics as API file systems
|
||||
for kernel-to-userspace and userspace-to-userpace interfaces. Some
|
||||
for kernel-to-userspace and userspace-to-userspace interfaces. Some
|
||||
of them may not be changed via mount units, and cannot be
|
||||
disabled. For a longer discussion see <ulink
|
||||
url="http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems">API
|
||||
|
||||
@@ -256,7 +256,7 @@
|
||||
<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. This key is not
|
||||
currently suported for <literal>tun</literal> or
|
||||
currently supported for <literal>tun</literal> or
|
||||
<literal>tap</literal> devices.
|
||||
</para>
|
||||
</listitem>
|
||||
@@ -268,7 +268,7 @@
|
||||
given, one is generated based on the interface name and
|
||||
the
|
||||
<citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
|
||||
This key is not currently suported for
|
||||
This key is not currently supported for
|
||||
<literal>tun</literal> or <literal>tap</literal> devices.
|
||||
</para>
|
||||
</listitem>
|
||||
@@ -556,7 +556,7 @@
|
||||
<varlistentry>
|
||||
<term><varname>PacketInfo=</varname></term>
|
||||
<listitem><para>Takes a boolean argument. Configures whether
|
||||
packets should be prepened with four extra bytes (two flag
|
||||
packets should be prepended with four extra bytes (two flag
|
||||
bytes and two protocol bytes). If disabled it indicates that
|
||||
the packets will be pure IP packets. Defaults to
|
||||
<literal>no</literal>.</para>
|
||||
|
||||
@@ -513,7 +513,7 @@
|
||||
<option>on-failure</option>, the service will be restarted
|
||||
when the process exits with a non-zero exit code, is
|
||||
terminated by a signal (including on core dump, but excluding
|
||||
the aforementiond four signals), when an operation (such as
|
||||
the aforementioned four signals), when an operation (such as
|
||||
service reload) times out, and when the configured watchdog
|
||||
timeout is triggered. If set to <option>on-abnormal</option>,
|
||||
the service will be restarted when the process is terminated
|
||||
@@ -891,7 +891,7 @@
|
||||
<title>Command lines</title>
|
||||
|
||||
<para>This section describes command line parsing and
|
||||
variable and specifier substitions for
|
||||
variable and specifier substitutions for
|
||||
<varname>ExecStart=</varname>,
|
||||
<varname>ExecStartPre=</varname>,
|
||||
<varname>ExecStartPost=</varname>,
|
||||
@@ -1131,7 +1131,7 @@ WantedBy=multi-user.target</programlisting>
|
||||
<varname>Type=</varname><option>oneshot</option> exists. Units
|
||||
of this type will wait until the process specified terminates
|
||||
and then fall back to being inactive. The following unit will
|
||||
perform a clenaup action:</para>
|
||||
perform a cleanup action:</para>
|
||||
|
||||
<programlisting>[Unit]
|
||||
Description=Cleanup old Foo data
|
||||
|
||||
@@ -226,7 +226,7 @@ int verify_units(char **filenames, SystemdRunningAs running_as, bool check_man)
|
||||
|
||||
r = manager_new(running_as, true, &m);
|
||||
if (r < 0)
|
||||
return log_error_errno(r, "Failed to initalize manager: %m");
|
||||
return log_error_errno(r, "Failed to initialize manager: %m");
|
||||
|
||||
log_debug("Starting manager...");
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user