Clarify journald.conf MaxLevelStore documentation

'stored on disk' gives the impression that this option affects only
permanent storage, even though it affects everything the journal
records, regardless of the storage type.
Use 'stored in the journal' to avoid confusion.
This commit is contained in:
Luca Boccassi 2020-01-16 16:24:07 +00:00 committed by Lennart Poettering
parent 251d3d20c3
commit c97ae2b290

View file

@ -365,7 +365,7 @@
<term><varname>MaxLevelWall=</varname></term> <term><varname>MaxLevelWall=</varname></term>
<listitem><para>Controls the maximum log level of messages <listitem><para>Controls the maximum log level of messages
that are stored on disk, forwarded to syslog, kmsg, the that are stored in the journal, forwarded to syslog, kmsg, the
console or wall (if that is enabled, see above). As argument, console or wall (if that is enabled, see above). As argument,
takes one of takes one of
<literal>emerg</literal>, <literal>emerg</literal>,
@ -381,8 +381,8 @@
are stored/forwarded, messages above are dropped. Defaults to are stored/forwarded, messages above are dropped. Defaults to
<literal>debug</literal> for <varname>MaxLevelStore=</varname> <literal>debug</literal> for <varname>MaxLevelStore=</varname>
and <varname>MaxLevelSyslog=</varname>, to ensure that the all and <varname>MaxLevelSyslog=</varname>, to ensure that the all
messages are written to disk and forwarded to syslog. Defaults messages are stored in the journal and forwarded to syslog.
to Defaults to
<literal>notice</literal> for <varname>MaxLevelKMsg=</varname>, <literal>notice</literal> for <varname>MaxLevelKMsg=</varname>,
<literal>info</literal> for <varname>MaxLevelConsole=</varname>, <literal>info</literal> for <varname>MaxLevelConsole=</varname>,
and <literal>emerg</literal> for and <literal>emerg</literal> for