shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-22 13:33:56 +03:00
Code

fix typos

Browse Source
This commit is contained in:
eggfly 2022-08-23 16:09:59 +08:00 committed by Zbigniew Jędrzejewski-Szmek
parent 9ed999cb5d
commit 6b5e82408d
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
NEWS
View File

@ -2488,7 +2488,7 @@ CHANGES WITH 248:
units.
systemd-oomd is now considered fully supported (the usual
backwards-compatiblity promises apply). Swap is not required for
backwards-compatibility promises apply). Swap is not required for
operation, but it is still recommended.
* systemd-timesyncd gained a new ConnectionRetrySec= setting which

2
man/org.freedesktop.resolve1.xml
View File

@ -606,7 +606,7 @@ node /org/freedesktop/resolve1 {
<para>The <varname>DNSSECStatistics</varname> property contains information about the DNSSEC
validations executed so far. It contains four 64-bit counters: the number of secure, insecure, bogus,
and indeterminate DNSSEC validations so far. The counters are increased for each validated RRset, and
each non-existance proof. The secure counter is increased for each operation that successfully verified
each non-existence proof. The secure counter is increased for each operation that successfully verified
a signed reply, the insecure counter is increased for each operation that successfully verified that an
unsigned reply is rightfully unsigned. The bogus counter is increased for each operation where the
validation did not check out and the data is likely to have been tempered with. Finally the

2
src/resolve/resolved-dns-cache.c
View File

@ -58,7 +58,7 @@ struct DnsCacheItem {
/* Returns true if this is a cache item created as result of an explicit lookup, or created as "side-effect"
* of another request. "Primary" entries will carry the full answer data (with NSEC, …) that can aso prove
* wildcard expansion, non-existance and such, while entries that were created as "side-effect" just contain
* wildcard expansion, non-existence and such, while entries that were created as "side-effect" just contain
* immediate RR data for the specified RR key, but nothing else. */
#define DNS_CACHE_ITEM_IS_PRIMARY(item) (!!(item)->answer)

2
src/udev/dmi_memory_id/dmi_memory_id.c
View File

@ -86,7 +86,7 @@ static bool verify_checksum(const uint8_t *buf, size_t len) {
}
/*
* Type-independant Stuff
* Type-independent Stuff
*/
static const char *dmi_string(const struct dmi_header *dm, uint8_t s) {

2
test/units/testsuite-62-4.service
View File

@ -1,6 +1,6 @@
# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=TEST-62-RESTRICT-IFACES-empty-assigment
Description=TEST-62-RESTRICT-IFACES-empty-assignment
[Service]
ExecStart=/bin/sh -c 'ping -c 1 -W 0.2 192.168.113.1'
ExecStart=/bin/sh -c 'ping -c 1 -W 0.2 192.168.113.5'

2
test/units/testsuite-62-5.service
View File

@ -1,6 +1,6 @@
# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=TEST-62-RESTRICT-IFACES-invert-assigment
Description=TEST-62-RESTRICT-IFACES-invert-assignment
[Service]
ExecStart=/bin/sh -c '! ping -c 1 -W 0.2 192.168.113.1'
ExecStart=/bin/sh -c 'ping -c 1 -W 0.2 192.168.113.5'