From 6dd3b818bbfc6a2c35e5a530186a8c0bc1e01118 Mon Sep 17 00:00:00 2001 From: Yu Watanabe Date: Sun, 28 Aug 2022 00:03:36 +0900 Subject: [PATCH] tree-wide: fix typo --- man/systemd-cgtop.xml | 2 +- src/libsystemd/sd-event/sd-event.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/man/systemd-cgtop.xml b/man/systemd-cgtop.xml index 074eeb246b..f08304d300 100644 --- a/man/systemd-cgtop.xml +++ b/man/systemd-cgtop.xml @@ -47,7 +47,7 @@ Resource usage is only accounted for control groups with the appropriate controllers turned on: cpu controller for CPU usage, memory controller for memory usage, - and io contoller for disk I/O consumption. If resource monitoring for these resources + and io controller for disk I/O consumption. If resource monitoring for these resources is required, it is recommended to add the CPUAccounting=1, MemoryAccounting=1 and IOAccounting=1 settings in the unit files in question. See diff --git a/src/libsystemd/sd-event/sd-event.c b/src/libsystemd/sd-event/sd-event.c index 027a8dffa1..b3b3d0b4d6 100644 --- a/src/libsystemd/sd-event/sd-event.c +++ b/src/libsystemd/sd-event/sd-event.c @@ -4531,8 +4531,8 @@ _public_ int sd_event_source_set_ratelimit_expire_callback(sd_event_source *s, s _public_ int sd_event_source_get_ratelimit(sd_event_source *s, uint64_t *ret_interval, unsigned *ret_burst) { assert_return(s, -EINVAL); - /* Querying whether an event source has ratelimiting configured is not a loggable offsense, hence - * don't use assert_return(). Unlike turning on ratelimiting it's not really a programming error */ + /* Querying whether an event source has ratelimiting configured is not a loggable offense, hence + * don't use assert_return(). Unlike turning on ratelimiting it's not really a programming error. */ if (!EVENT_SOURCE_CAN_RATE_LIMIT(s->type)) return -EDOM; -- 2.25.1