mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-10-26 08:55:18 +03:00
man: remove some trailing whitespace
This commit is contained in:
parent
23a2badf74
commit
9854ac4af4
@ -87,7 +87,7 @@
|
|||||||
which will be processed. Core dumps exceeding this size
|
which will be processed. Core dumps exceeding this size
|
||||||
may be stored, but the backtrace will not be generated.
|
may be stored, but the backtrace will not be generated.
|
||||||
Like other sizes in this same config file, the usual
|
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>
|
G, T, P, and E.)</para>
|
||||||
|
|
||||||
<para>Setting <varname>Storage=none</varname> and <varname>ProcessSizeMax=0</varname>
|
<para>Setting <varname>Storage=none</varname> and <varname>ProcessSizeMax=0</varname>
|
||||||
@ -100,7 +100,7 @@
|
|||||||
<term><varname>JournalSizeMax=</varname></term>
|
<term><varname>JournalSizeMax=</varname></term>
|
||||||
|
|
||||||
<listitem><para>The maximum (uncompressed) size in bytes of a
|
<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>.
|
<option>ProcessSizeMax=</option></para></listitem>.
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
@ -78,8 +78,8 @@
|
|||||||
the kernel log buffer, or a syslog socket will still work). Defaults to <literal>auto</literal> in
|
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>
|
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
|
<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
|
<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
|
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>
|
on boot via <literal>systemd-journal-flush.service</literal>.</para>
|
||||||
|
|
||||||
|
@ -80,8 +80,8 @@
|
|||||||
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> to configure
|
<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>
|
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
|
<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
|
<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
|
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>
|
on boot via <literal>systemd-journal-flush.service</literal>.</para>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user