mirror of
https://github.com/Dasharo/systemd.git
synced 2026-03-06 15:02:31 -08:00
codespell: fix spelling errors
This commit is contained in:
Ben Boeckel
committed by
Zbigniew Jędrzejewski-Szmek
Zbigniew Jędrzejewski-Szmek
parent
51aba17b88
commit
5238e95759
12
NEWS
12
NEWS
@@ -753,7 +753,7 @@ CHANGES WITH 240:
|
||||
* Journal messages that are generated whenever a unit enters the failed
|
||||
state are now tagged with a unique MESSAGE_ID. Similarly, messages
|
||||
generated whenever a service process exits are now made recognizable,
|
||||
too. A taged message is also emitted whenever a unit enters the
|
||||
too. A tagged message is also emitted whenever a unit enters the
|
||||
"dead" state on success.
|
||||
|
||||
* systemd-run gained a new switch --working-directory= for configuring
|
||||
@@ -995,7 +995,7 @@ CHANGES WITH 239:
|
||||
not created by systemd-sysusers anymore.
|
||||
|
||||
NOTE: This has a chance of breaking nss-ldap and similar NSS modules
|
||||
that embedd a network facing module into any process using getpwuid()
|
||||
that embed a network facing module into any process using getpwuid()
|
||||
or related call: the dynamic allocation of the user ID for
|
||||
systemd-resolved.service means the service manager has to check NSS
|
||||
if the user name is already taken when forking off the service. Since
|
||||
@@ -1264,7 +1264,7 @@ CHANGES WITH 239:
|
||||
PrivateDevices=, ProtectSystem=, …) are used. This option is hence
|
||||
primarily useful for services that do not use any of the other file
|
||||
system namespacing options. One such service is systemd-udevd.service
|
||||
wher this is now used by default.
|
||||
where this is now used by default.
|
||||
|
||||
* ConditionSecurity= gained a new value "uefi-secureboot" that is true
|
||||
when the system is booted in UEFI "secure mode".
|
||||
@@ -2247,7 +2247,7 @@ CHANGES WITH 234:
|
||||
/etc/machine-id. If the machine ID could not be determined,
|
||||
$KERNEL_INSTALL_MACHINE_ID will be empty. Plugins should not put
|
||||
anything in the entry directory (passed as the second argument) if
|
||||
$KERNEL_INSTALL_MACHINE_ID is empty. For backwards compatiblity, a
|
||||
$KERNEL_INSTALL_MACHINE_ID is empty. For backwards compatibility, a
|
||||
temporary directory is passed as the entry directory and removed
|
||||
after all the plugins exit.
|
||||
|
||||
@@ -5975,7 +5975,7 @@ CHANGES WITH 214:
|
||||
* We temporarily dropped the "-l" switch for fsck invocations,
|
||||
since they collide with the flock() logic above. util-linux
|
||||
upstream has been changed already to avoid this conflict,
|
||||
and we will readd "-l" as soon as util-linux with this
|
||||
and we will re-add "-l" as soon as util-linux with this
|
||||
change has been released.
|
||||
|
||||
* The dependency on libattr has been removed. Since a long
|
||||
@@ -6261,7 +6261,7 @@ CHANGES WITH 213:
|
||||
where the local administrator's configuration in /etc always
|
||||
overrides any other settings.
|
||||
|
||||
Contributions fron: Ali H. Caliskan, Alison Chaiken, Bas van
|
||||
Contributions from: Ali H. Caliskan, Alison Chaiken, Bas van
|
||||
den Berg, Brandon Philips, Cristian Rodríguez, Daniel Buch,
|
||||
Dan Kilman, Dave Reisner, David Härdeman, David Herrmann,
|
||||
David Strauss, Dimitris Spingos, Djalal Harouni, Eelco
|
||||
|
||||
2
README
2
README
@@ -182,7 +182,7 @@ REQUIREMENTS:
|
||||
To build in directory build/:
|
||||
meson build/ && ninja -C build
|
||||
|
||||
Any configuration options can be specfied as -Darg=value... arguments
|
||||
Any configuration options can be specified as -Darg=value... arguments
|
||||
to meson. After the build directory is initially configured, meson will
|
||||
refuse to run again, and options must be changed with:
|
||||
mesonconf -Darg=value...
|
||||
|
||||
10
TODO
10
TODO
@@ -163,7 +163,7 @@ Features:
|
||||
selected user is resolvable in the service even if it ships its own /etc/passwd)
|
||||
|
||||
* Fix DECIMAL_STR_MAX or DECIMAL_STR_WIDTH. One includes a trailing NUL, the
|
||||
other doesn't. What a desaster. Probably to exclude it. Also
|
||||
other doesn't. What a disaster. Probably to exclude it. Also
|
||||
DECIMAL_STR_WIDTH should probably add an extra "-" into account for negative
|
||||
numbers.
|
||||
|
||||
@@ -192,7 +192,7 @@ Features:
|
||||
specific paths only like this.
|
||||
|
||||
* add CopyFile= or so as unit file setting that may be used to copy files or
|
||||
directory trees from the host to te services RootImage= and RootDirectory=
|
||||
directory trees from the host to the services RootImage= and RootDirectory=
|
||||
environment. Which we can use for /etc/machine-id and in particular
|
||||
/etc/resolv.conf. Should be smart and do something useful on read-only
|
||||
images, for example fallback to read-only bind mounting the file instead.
|
||||
@@ -452,7 +452,7 @@ Features:
|
||||
* PID 1 should send out sd_notify("WATCHDOG=1") messages (for usage in the --user mode, and when run via nspawn)
|
||||
|
||||
* there's probably something wrong with having user mounts below /sys,
|
||||
as we have for debugfs. for exmaple, src/core/mount.c handles mounts
|
||||
as we have for debugfs. for example, src/core/mount.c handles mounts
|
||||
prefixed with /sys generally special.
|
||||
http://lists.freedesktop.org/archives/systemd-devel/2015-June/032962.html
|
||||
|
||||
@@ -514,7 +514,7 @@ Features:
|
||||
|
||||
* systemctl: if some operation fails, show log output?
|
||||
|
||||
* systemctl edit: use equvalent of cat() to insert existing config as a comment, prepended with #.
|
||||
* systemctl edit: use equivalent of cat() to insert existing config as a comment, prepended with #.
|
||||
Upon editor exit, lines with one # are removed, lines with two # are left with one #, etc.
|
||||
|
||||
* exponential backoff in timesyncd when we cannot reach a server
|
||||
@@ -726,7 +726,7 @@ Features:
|
||||
- sd-journal: speed up sd_journal_get_data() with transparent hash table in bg
|
||||
- journald: when dropping msgs due to ratelimit make sure to write
|
||||
"dropped %u messages" not only when we are about to print the next
|
||||
message that works, but alraedy after a short tiemout
|
||||
message that works, but already after a short timeout
|
||||
- check if we can make journalctl by default use --follow mode inside of less if called without args?
|
||||
- maybe add API to send pairs of iovecs via sd_journal_send
|
||||
- journal: add a setgid "systemd-journal" utility to invoke from libsystemd-journal, which passes fds via STDOUT and does PK access
|
||||
|
||||
@@ -384,7 +384,7 @@ The following "tags" are possible:
|
||||
- "split-usr" — /usr is a separate file system and was not mounted when systemd
|
||||
was booted
|
||||
- "cgroups-missing" — the kernel was compiled without cgroup support or access
|
||||
to expected interface files is resticted
|
||||
to expected interface files is restricted
|
||||
- "var-run-bad" — /var/run is not a symlink to /run
|
||||
- "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with
|
||||
NFS or user namespaces) is not 65534
|
||||
|
||||
@@ -154,7 +154,7 @@ strategies to avoid these issues:
|
||||
in these directories when they are no longer needed, in particular when the
|
||||
program dies unexpectedly. Note: this strategy is only really suitable for
|
||||
packages that operate in a "system wide singleton" fashion with "long"
|
||||
persistance of its data or state, i.e. as opposed to programs that run in
|
||||
persistence of its data or state, i.e. as opposed to programs that run in
|
||||
multiple parallel or short-living instances. This is because a private
|
||||
directory under `/run` (and the other mentioned directories) is itself
|
||||
system and package specific singleton with greater longevity.
|
||||
|
||||
@@ -60,7 +60,7 @@
|
||||
# Trackpoint const accel settings are specified as
|
||||
# POINTINGSTICK_CONST_ACCEL=<accel>
|
||||
#
|
||||
# Where <accel> is a floating point number, using a '.' seperator, specifying
|
||||
# Where <accel> is a floating point number, using a '.' separator, specifying
|
||||
# by how much to multiply deltas generated by the pointingstick to get
|
||||
# normalized deltas.
|
||||
#
|
||||
|
||||
@@ -255,7 +255,7 @@
|
||||
through external means. The <option>dns</option> command expects IPv4 or IPv6 address specifications of DNS
|
||||
servers to use. The <option>domain</option> command expects valid DNS domains, possibly prefixed with
|
||||
<literal>~</literal>, and configures a per-interface search or route-only domain. The
|
||||
<option>default-route</option> command expects a boolean paremeter, and configures whether the link may be
|
||||
<option>default-route</option> command expects a boolean parameter, and configures whether the link may be
|
||||
used as default route for DNS lookups, i.e. if it is suitable for lookups on domains no other link explicitly
|
||||
is configured for. The <option>llmnr</option>, <option>mdns</option>, <option>dnssec</option> and
|
||||
<option>dnsovertls</option> commands may be used to configure the per-interface LLMNR, MulticastDNS, DNSSEC
|
||||
|
||||
@@ -277,7 +277,7 @@
|
||||
</para>
|
||||
|
||||
<para>Equivalent to <constant>SD_BUS_SIGNAL_WITH_NAMES()</constant> with the
|
||||
<replaceable>names</replaceable> paramater unset (i.e. no parameter names).</para>
|
||||
<replaceable>names</replaceable> parameter unset (i.e. no parameter names).</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@@ -44,7 +44,7 @@
|
||||
|
||||
<para><function>sd_bus_close()</function> disconnects the specified bus connection. When this call is invoked and
|
||||
the specified bus object refers to an active connection it is immediately terminated. No further messages may be
|
||||
sent or receieved on it. Any messages queued in the bus object (both incoming and outgoing) are released. If
|
||||
sent or received on it. Any messages queued in the bus object (both incoming and outgoing) are released. If
|
||||
invoked on <constant>NULL</constant> bus object or when the bus connection is already closed this function executes
|
||||
no operation. This call does not free or unreference the bus object itself. Use
|
||||
<citerefentry><refentrytitle>sd_bus_unref</refentrytitle><manvolnum>3</manvolnum></citerefentry> for that.</para>
|
||||
|
||||
@@ -116,7 +116,7 @@
|
||||
project='man-pages'><refentrytitle>printf</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||
format string <parameter>format</parameter> and corresponding arguments.
|
||||
<literal>%m</literal> may be used in the format string to refer to the error
|
||||
string corresponding to the specified errno code. The error message is initalized
|
||||
string corresponding to the specified errno code. The error message is initialized
|
||||
using the error identifier generated from <constant>error</constant> and the
|
||||
formatted string. (If <parameter>error</parameter> is zero, no error is actually
|
||||
set, and an error reply with no information is created.)</para>
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
<refnamediv>
|
||||
<refname>sd_bus_message_rewind</refname>
|
||||
|
||||
<refpurpose>Return to begining of message or current container</refpurpose>
|
||||
<refpurpose>Return to beginning of message or current container</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
@@ -38,7 +38,7 @@
|
||||
<title>Description</title>
|
||||
|
||||
<para><function>sd_bus_message_rewind()</function> moves the "read pointer" in the message
|
||||
<parameter>m</parameter> to either the begining of the message (if
|
||||
<parameter>m</parameter> to either the beginning of the message (if
|
||||
<parameter>complete</parameter> is true) or to the beginning of the currently open container. If
|
||||
no container is open, <parameter>complete</parameter> has no effect.</para>
|
||||
</refsect1>
|
||||
|
||||
@@ -70,7 +70,7 @@
|
||||
<listitem><para><parameter>m</parameter> or both <parameter>type</parameter> and
|
||||
<parameter>contents</parameter> are <constant>NULL</constant>.</para>
|
||||
|
||||
<para>Arguments do not satisfy other contraints listed above.</para>
|
||||
<para>Arguments do not satisfy other constraints listed above.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@@ -337,7 +337,7 @@ $ eog targets.svg</programlisting>
|
||||
</example>
|
||||
|
||||
<para>Note that this verb prints the list that is compiled into <command>systemd-analyze</command>
|
||||
itself, and does not comunicate with the running manager. Use
|
||||
itself, and does not communicate with the running manager. Use
|
||||
<programlisting>systemctl [--user] [--global] show -p UnitPath --value</programlisting>
|
||||
to retrieve the actual list that the manager uses, with any empty directories omitted.</para>
|
||||
</refsect2>
|
||||
|
||||
@@ -357,7 +357,7 @@
|
||||
|
||||
<para><command>systemd-boot</command> implements a simple boot counting mechanism on top of the <ulink
|
||||
url="https://systemd.io/BOOT_LOADER_SPECIFICATION">Boot Loader Specification</ulink>, for automatic and unattended
|
||||
fallback to older kernel versions/boot loader entries when a specific entry continously fails. Any boot loader
|
||||
fallback to older kernel versions/boot loader entries when a specific entry continuously fails. Any boot loader
|
||||
entry file and unified kernel image file that contains a <literal>+</literal> followed by one or two numbers (if
|
||||
two they need to be separated by a <literal>-</literal>), before the <filename>.conf</filename> or
|
||||
<filename>.efi</filename> suffix is subject to boot counting: the first of the two numbers ('tries left') is
|
||||
|
||||
@@ -234,7 +234,7 @@
|
||||
<term><varname>root=</varname></term>
|
||||
|
||||
<listitem><para>When used with the special value <literal>gpt-auto</literal>, automatic discovery of
|
||||
the root parition based on the GPT partition type is enabled. Any other value disables this
|
||||
the root partition based on the GPT partition type is enabled. Any other value disables this
|
||||
generator.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@@ -55,7 +55,7 @@
|
||||
one is necessary to access some network resources. When used, all other interfaces are ignored.
|
||||
This option may be used more than once to wait for multiple network interfaces. When this
|
||||
option is specified multiple times, then <command>systemd-networkd-wait-online</command> waits
|
||||
for all specified interfaces to be online. Optinally, required minimum operational state can be
|
||||
for all specified interfaces to be online. Optionally, required minimum operational state can be
|
||||
specified after a colon <literal>:</literal>. Please see
|
||||
<citerefentry><refentrytitle>networkctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
||||
for possible operational states. If the operational state is not specified here, then
|
||||
|
||||
@@ -163,7 +163,7 @@
|
||||
<listitem><para>Otherwise the query is failed as no suitable DNS servers could be determined.</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>The "DNS default route" option is a boolean setting configureable with <command>resolvectl</command> or in
|
||||
<para>The "DNS default route" option is a boolean setting configurable with <command>resolvectl</command> or in
|
||||
<filename>.network</filename> files. If not set, it is implicitly determined based on the configured DNS domains
|
||||
for a link: if there's any route-only domain (not matching <literal>~.</literal>) it defaults to false, otherwise
|
||||
to true.</para>
|
||||
|
||||
@@ -33,7 +33,7 @@
|
||||
|
||||
<para><emphasis>Using this service is not recommended.</emphasis> There can be no guarantee that hardware
|
||||
is fully discovered at any specific time, because the kernel does hardware detection asynchronously, and
|
||||
certain busses and devices take a very long time to become ready, and also additional hardware may be
|
||||
certain buses and devices take a very long time to become ready, and also additional hardware may be
|
||||
plugged in at any time. Instead, services should subscribe to udev events and react to any new hardware as
|
||||
it is discovered. Services that, based on configuration, expect certain devices to appear, may warn or
|
||||
report failure after a timeout. This timeout should be tailored to the hardware type. Waiting for
|
||||
|
||||
@@ -1304,7 +1304,7 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
|
||||
running in user mode, or in system mode, but without the <constant>CAP_SYS_ADMIN</constant> capability
|
||||
(e.g. setting <varname>User=nobody</varname>), <varname>NoNewPrivileges=yes</varname> is implied. By default,
|
||||
no restrictions apply, all address families are accessible to processes. If assigned the empty string, any
|
||||
previous address familiy restriction changes are undone. This setting does not affect commands prefixed with
|
||||
previous address family restriction changes are undone. This setting does not affect commands prefixed with
|
||||
<literal>+</literal>.</para>
|
||||
|
||||
<para>Use this option to limit exposure of processes to remote access, in particular via exotic and sensitive
|
||||
@@ -1928,7 +1928,7 @@ SystemCallErrorNumber=EPERM</programlisting>
|
||||
<para>Note that services which specify <option>DefaultDependencies=no</option> and use
|
||||
<varname>StandardInput=</varname> or <varname>StandardOutput=</varname> with
|
||||
<option>tty</option>/<option>tty-force</option>/<option>tty-fail</option>, should specify
|
||||
<option>After=systemd-vconsole-setup.service</option>, to make sure that the tty intialization is
|
||||
<option>After=systemd-vconsole-setup.service</option>, to make sure that the tty initialization is
|
||||
finished before they start.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@@ -312,7 +312,7 @@
|
||||
<listitem><para>The file system will be initialized
|
||||
on the device. If the device is not "empty", i.e. it contains any signature,
|
||||
the operation will be skipped. It is hence expected that this option
|
||||
remains set even after the device has been initalized.</para>
|
||||
remains set even after the device has been initialized.</para>
|
||||
|
||||
<para>Note that this option can only be used in
|
||||
<filename>/etc/fstab</filename>, and will be ignored when part of the
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user