summaryrefslogtreecommitdiffstats
path: root/man/journalctl.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2022-03-04 16:39:34 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2022-03-04 16:44:02 +0100
commit367a5e8a67bbc2b5e03ca1a3e5a601ef49b5bd2a (patch)
tree14bdd56f3de0a9e13c6559a66f394e4cd827a9e7 /man/journalctl.xml
parentman: describe UNIT=/USER_UNIT= (diff)
downloadsystemd-367a5e8a67bbc2b5e03ca1a3e5a601ef49b5bd2a.tar.xz
systemd-367a5e8a67bbc2b5e03ca1a3e5a601ef49b5bd2a.zip
journalctl: advertise --header a bit more
Fixes #2738.
Diffstat (limited to 'man/journalctl.xml')
-rw-r--r--man/journalctl.xml16
1 files changed, 9 insertions, 7 deletions
diff --git a/man/journalctl.xml b/man/journalctl.xml
index 9e784f3d3c..424acc9f16 100644
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -85,10 +85,10 @@
<option>--boot</option>, <option>--unit=</option>, etc., to
further limit what entries will be shown (logical AND).</para>
- <para>Output is interleaved from all accessible journal files,
- whether they are rotated or currently being written, and
- regardless of whether they belong to the system itself or are
- accessible user journals.</para>
+ <para>Output is interleaved from all accessible journal files, whether they are rotated or currently
+ being written, and regardless of whether they belong to the system itself or are accessible user
+ journals. The <option>--header</option> option can be used to identify which files
+ <emphasis>are</emphasis> being shown.</para>
<para>The set of journal files which will be used can be
modified using the <option>--user</option>,
@@ -794,9 +794,11 @@
<varlistentry>
<term><option>--header</option></term>
- <listitem><para>Instead of showing journal contents, show
- internal header information of the journal fields
- accessed.</para></listitem>
+ <listitem><para>Instead of showing journal contents, show internal header information of the journal
+ fields accessed.</para>
+
+ <para>This option is particularly useful when trying to identify out-of-order journal entries, as
+ happens for example when the machine is booted with the wrong system time.</para></listitem>
</varlistentry>
<varlistentry>