diff options
| author | Lennart Poettering <lennart@poettering.net> | 2021-05-10 23:08:58 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2021-05-10 23:10:44 +0200 |
| commit | 9854ac4af422359514334bdeca6927d7d9f92af7 (patch) | |
| tree | 62d20e6f3886ff70cabba2d2ccb8c3a5242b5972 | |
| parent | 23a2badf7445b76b93d2ea2da9e24f7543dc0e0a (diff) | |
| download | systemd-9854ac4af422359514334bdeca6927d7d9f92af7.tar.gz | |
man: remove some trailing whitespace
| -rw-r--r-- | man/coredump.conf.xml | 4 | ||||
| -rw-r--r-- | man/journald.conf.xml | 4 | ||||
| -rw-r--r-- | man/systemd-journald.service.xml | 4 |
3 files changed, 6 insertions, 6 deletions
diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml index 5f1b4ce028..d0f46cfe05 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.)</para> <para>Setting <varname>Storage=none</varname> and <varname>ProcessSizeMax=0</varname> @@ -100,7 +100,7 @@ <term><varname>JournalSizeMax=</varname></term> <listitem><para>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 <option>ProcessSizeMax=</option></para></listitem>. </varlistentry> diff --git a/man/journald.conf.xml b/man/journald.conf.xml index 06583d5ed3..4b0dd90cbb 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 <literal>auto</literal> in the default journal namespace, and <literal>persistent</literal> in all others.</para> - <para>Note that journald will initially use volatile storage, until a call to - <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause + <para>Note that journald will initially use volatile storage, until a call to + <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause it to switch to persistent logging (under the conditions mentioned above). This is done automatically on boot via <literal>systemd-journal-flush.service</literal>.</para> diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index b66e6ea8eb..e797ca6e00 100644 --- a/man/systemd-journald.service.xml +++ b/man/systemd-journald.service.xml @@ -80,8 +80,8 @@ <citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> to configure where log data is placed, independently of the existence of <filename>/var/log/journal/</filename>.</para> - <para>Note that journald will initially use volatile storage, until a call to - <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause + <para>Note that journald will initially use volatile storage, until a call to + <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause it to switch to persistent logging (under the conditions mentioned above). This is done automatically on boot via <literal>systemd-journal-flush.service</literal>.</para> |