From: Lennart Poettering Date: Mon, 10 May 2021 21:08:58 +0000 (+0200) Subject: man: remove some trailing whitespace X-Git-Tag: v249-rc1~252^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F19575%2Fhead;p=thirdparty%2Fsystemd.git man: remove some trailing whitespace --- diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml index 5f1b4ce028c..d0f46cfe053 100644 --- a/man/coredump.conf.xml +++ b/man/coredump.conf.xml @@ -87,7 +87,7 @@ which will be processed. Core dumps exceeding this size may be stored, but the backtrace will not be generated. Like other sizes in this same config file, the usual - suffixes to the base of 1024 are allowed (B, K, M, + suffixes to the base of 1024 are allowed (B, K, M, G, T, P, and E.) Setting Storage=none and ProcessSizeMax=0 @@ -100,7 +100,7 @@ JournalSizeMax= The maximum (uncompressed) size in bytes of a - core to be saved. Unit suffixes are allowed just as in + core to be saved. Unit suffixes are allowed just as in . diff --git a/man/journald.conf.xml b/man/journald.conf.xml index 06583d5ed3f..4b0dd90cbbd 100644 --- a/man/journald.conf.xml +++ b/man/journald.conf.xml @@ -78,8 +78,8 @@ the kernel log buffer, or a syslog socket will still work). Defaults to auto in the default journal namespace, and persistent in all others. - Note that journald will initially use volatile storage, until a call to - journalctl --flush (or sending SIGUSR1 to journald) will cause + Note that journald will initially use volatile storage, until a call to + journalctl --flush (or sending SIGUSR1 to journald) will cause it to switch to persistent logging (under the conditions mentioned above). This is done automatically on boot via systemd-journal-flush.service. diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index b66e6ea8ebc..e797ca6e00a 100644 --- a/man/systemd-journald.service.xml +++ b/man/systemd-journald.service.xml @@ -80,8 +80,8 @@ journald.conf5 to configure where log data is placed, independently of the existence of /var/log/journal/. - Note that journald will initially use volatile storage, until a call to - journalctl --flush (or sending SIGUSR1 to journald) will cause + Note that journald will initially use volatile storage, until a call to + journalctl --flush (or sending SIGUSR1 to journald) will cause it to switch to persistent logging (under the conditions mentioned above). This is done automatically on boot via systemd-journal-flush.service.