journalctl: add --priority= switch for filtering by priority

[elogind.git] / man / journald.conf.xml

diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 72d81fbdf454d668173087bb96eed00a4a37c561..d7caea83cce6018be4d8b6a1eaba63c403b917c2 100644 (file)
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -174,7 +174,7 @@
                                 influences the granularity in which
                                 disk space is made available through
                                 rotation, i.e. deletion of historic
-                                data. Defaults to one eigth of the
+                                data. Defaults to one eighth of the
                                 values configured with
                                 <varname>SystemMaxUse=</varname> and
                                 <varname>RuntimeMaxUse=</varname>, so
@@ -276,7 +276,7 @@
                                 <listitem><para>Controls whether
                                 kernel log messages shall be stored in
                                 the journal. Takes a boolean argument
-                                and defaults to enabled. Note that
+                                and defaults to disabled. Note that
                                 currently only one userspace service
                                 can read kernel messages at a time,
                                 which means that kernel log message
@@ -293,7 +293,7 @@
                                 <listitem><para>Controls where to
                                 store journal data. One of
                                 <literal>volatile</literal>,
-                                <literal>permanent</literal>,
+                                <literal>persistent</literal>,
                                 <literal>auto</literal> and
                                 <literal>none</literal>. If
                                 <literal>volatile</literal> journal
@@ -302,7 +302,7 @@
                                 <filename>/run/log/journal</filename>
                                 hierarchy (which is created if
                                 needed). If
-                                <literal>permanent</literal> data will
+                                <literal>persistent</literal> data will
                                 be stored preferably on disk,
                                 i.e. below the
                                 <filename>/var/log/journal</filename>
@@ -313,11 +313,11 @@
                                 early boot and if the disk is not
                                 writable. <literal>auto</literal> is
                                 similar to
-                                <literal>permanent</literal> but the
+                                <literal>persistent</literal> but the
                                 directory
                                 <filename>/var/log/journal</filename>
                                 is not created if needed, so that its
-                                existance controls where log data
+                                existence controls where log data
                                 goes. <literal>none</literal> turns
                                 off all storage, all log data received
                                 will be dropped. Forwarding to other