shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-02-27 13:57:26 +03:00
Code

tree-wide: fix typos

Browse Source
This commit is contained in:
Yu Watanabe 2020-12-02 17:53:32 +09:00 committed by Zbigniew Jędrzejewski-Szmek
parent ebef02dd8f
commit da115b935a
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man/crypttab.xml
View File

@ -80,7 +80,7 @@
allows the implementation of a service to provide key information dynamically, at the moment when it is allows the implementation of a service to provide key information dynamically, at the moment when it is
needed. For details see below.</para></listitem> needed. For details see below.</para></listitem>
<listitem><para>The fourth field, if present, is a comma-delimited list of options. The suppported <listitem><para>The fourth field, if present, is a comma-delimited list of options. The supported
options are listed below.</para></listitem> options are listed below.</para></listitem>
</orderedlist> </orderedlist>

2
src/libsystemd/sd-event/test-event.c
View File

@ -667,7 +667,7 @@ static void test_ratelimit(void) {
log_info("ratelimit_time_handler: called %d times, event source got ratelimited", count); log_info("ratelimit_time_handler: called %d times, event source got ratelimited", count);
assert_se(count == 10); assert_se(count == 10);
/* In order to get rid of active rate limit client needs to disable it explicitely */ /* In order to get rid of active rate limit client needs to disable it explicitly */
assert_se(sd_event_source_set_ratelimit(s, 0, 0) >= 0); assert_se(sd_event_source_set_ratelimit(s, 0, 0) >= 0);
assert_se(!sd_event_source_is_ratelimited(s)); assert_se(!sd_event_source_is_ratelimited(s));

2
test/units/testsuite-16.sh
View File

@ -37,7 +37,7 @@ wait_for success_runtime
wait_for success_stop wait_for success_stop
# These ensure that EXTEND_TIMEOUT_USEC will still timeout in the # These ensure that EXTEND_TIMEOUT_USEC will still timeout in the
# approprate stage, after the stage limit, when the EXTEND_TIMEOUT_USEC # appropriate stage, after the stage limit, when the EXTEND_TIMEOUT_USEC
# message isn't sent within the extend timeout interval. # message isn't sent within the extend timeout interval.
wait_for fail_start startfail wait_for fail_start startfail