X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fjournalctl.xml;h=c8559a0cb01740b4987eb52e8b0437082e859883;hb=dc7adf202b82fc0054c457ce6ca3bcedb88dde57;hp=0e779b952c0813538ce47af48320eccd5339d858;hpb=a331b5e6d4724365bad9edeb9420c7e26e7f50da;p=elogind.git
diff --git a/man/journalctl.xml b/man/journalctl.xml
index 0e779b952..c8559a0cb 100644
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -233,53 +233,137 @@
Controls the
formatting of the journal entries that
- are shown. Takes one of
- short,
- short-monotonic,
- verbose,
- export,
- json,
- json-pretty,
- json-sse,
- cat. short
- is the default and generates an output
- that is mostly identical to the
- formatting of classic syslog
- files, showing one line per journal
- entry. short-monotonic
- is very similar but shows monotonic
- timestamps instead of wallclock
- timestamps. verbose
- shows the full structured entry items
- with all
- fields. export
- serializes the journal into a binary
- (but mostly text-based) stream
- suitable for backups and network
- transfer (see Journal
- Export Format for more
- information). json
- formats entries as JSON data
- structures, one per
- line (see Journal
- JSON Format for more
- information). json-pretty
- also formats entries as JSON data
- structures, but formats them in
- multiple lines in order to make them
- more readable for
- humans. json-sse
- also formats entries as JSON data
- structures, but wraps them in a format
- suitable for Server-Sent
- Events. cat
- generates a very terse output only
- showing the actual message of each
- journal entry with no meta data, not
- even a timestamp.
+ are shown. Takes one of the following options:
+
+
+
+
+
+
+
+ is the default
+ and generates an output
+ that is mostly identical
+ to the formatting of
+ classic syslog files,
+ showing one line per
+ journal entry.
+
+
+
+
+
+
+
+
+ is very similar
+ but shows monotonic
+ timestamps instead of
+ wallclock timestamps.
+
+
+
+
+
+
+
+
+
+ is very similar
+ but shows ISO 8601
+ wallclock timestamps.
+
+
+
+
+
+
+
+
+
+ shows the
+ full-structured entry
+ items with all fields.
+
+
+
+
+
+
+
+
+
+ serializes the
+ journal into a binary
+ (but mostly text-based)
+ stream suitable for
+ backups and network
+ transfer (see Journal
+ Export Format
+ for more
+ information).
+
+
+
+
+
+
+
+
+ formats entries
+ as JSON data structures,
+ one per line (see Journal
+ JSON Format for
+ more information).
+
+
+
+
+
+
+
+
+ formats entries as
+ JSON data structures,
+ but formats them in
+ multiple lines in order
+ to make them more
+ readable for humans.
+
+
+
+
+
+
+
+
+ formats entries as
+ JSON data structures,
+ but wraps them in a
+ format suitable for Server-Sent
+ Events.
+
+
+
+
+
+
+
+
+ generates a very
+ terse output only
+ showing the actual
+ message of each journal
+ entry with no meta data,
+ not even a timestamp.
+
+
+
+
+
@@ -327,42 +411,50 @@
-
-
+
+
- Show messages from the specified
- boot ID or from
- current boot if no ID
- is given. This will add a match for
+ Show messages from a specific
+ boot. This will add a match for
_BOOT_ID=.
- The argument is a 128 bit ID given in
- short or UUID form and optionally followed by
- :n which identifies the nth
- boot relative to the boot ID given to the left
- of :. Supplying a negative
- value for n will look for a past boot and a
- positive value for a future boot. The boot IDs
- are searched for in chronological order. If no
- number is provided after :,
- -1 is assumed. A value of 0
- is valid and equivalent to omitting
- :0.
-
- Alternatively, the argument may constist
- only of :n. In this case, a
- positive value will look up the nth boot
- starting from the beginning of the jouranl, a
- negative value will look up a previous boot
- relative to the current boot. :0
- will look for the current boot ID. Thus,
- :1 is the first boot found in
- the journal, :2 the second
- and so on; while :-1 is the
- previous boot, :-2 the boot
- before that and so on. Omitting a value after
- : will look for the previous
- boot.
+ The argument may be empty, in which case
+ logs for the current boot will be shown.
+
+ If the boot ID is omitted, a positive
+ offset will look up
+ the boots starting from the beginning of the
+ journal, and a equal-or-less-than zero
+ offset will look up
+ boots starting from the end of the
+ journal. Thus, 1 means the
+ first boot found in the journal in the
+ chronological order, 2 the
+ second and so on; while -0
+ is the last boot, -1 the
+ boot before that, and so on. An empty
+ offset is equivalent
+ to specifying -0, except
+ when the current boot is not the last boot
+ (e.g. because was
+ specified to look at logs from a different
+ machine).
+
+ If the 32 character
+ ID is specified, it
+ may optionally be followed by
+ offset which
+ identifies the boot relative to the one given by
+ boot ID. Negative
+ values mean earlier boots and a positive values
+ mean later boots. If
+ offset is not
+ specified, a value of zero is assumed and the
+ logs for the boot given by
+ ID are shown.
+
+
+
@@ -450,6 +542,16 @@
cursor.
+
+
+
+ Start showing entries from the
+ location in the journal
+ after the location
+ specified by the this cursor.
+
+
+
@@ -749,9 +851,9 @@
journalctl /dev/sda
- Show all kernel logs from last boot:
+ Show all kernel logs from previous boot:
- journalctl -k -b :
+ journalctl -k -b -1