X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fjournalctl.xml;h=011fea28004e9f32168aa6f400518076b2a1686b;hp=b8b29b4cb5da2e6f74c9dd5193e3fbc61b356a0f;hb=e7176abbe818c75c6acd90227a7a84c3e05fee31;hpb=77a9e8de6572db6ba5ca49023937b67fc835f356
diff --git a/man/journalctl.xml b/man/journalctl.xml
index b8b29b4cb..011fea280 100644
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -104,7 +104,7 @@
All users are granted access to their private
per-user journals. However, by default, only root and
- users who are members of the adm
+ users who are members of the systemd-journal
group get access to the system journal and the
journals of other users.
@@ -152,11 +152,20 @@
-
+
+
+
+ Ellipsize fields when
+ they do not fit in available columns.
+ The default is to show full fields,
+ allowing them to wrap or be truncated
+ by the pager if one is used.
- Show all (printable) fields in
- full.
+ The old options
+ /
+ are not useful anymore, except to undo
+ .
@@ -233,53 +242,150 @@
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 ISO 8601
+ wallclock timestamps.
+
+
+
+
+
+
+
+
+
+ is very similar,
+ but shows timestamps
+ with full microsecond
+ precision.
+
+
+
+
+
+
+
+
+
+ is very similar,
+ but shows monotonic
+ timestamps instead of
+ 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.
+
+
+
+
+
@@ -295,7 +401,7 @@
context of an error or log event,
possible solutions, as well as
pointers to support forums, developer
- documentation and any other relevant
+ documentation, and any other relevant
manuals. Note that help texts are not
available for all messages, but only
for selected ones. For more
@@ -303,7 +409,14 @@
please refer to the Message
Catalog Developer
- Documentation.
+ Documentation.
+
+ Note: when attaching
+ journalctl output
+ to bug reports, please do
+ not use
+ .
+
@@ -327,23 +440,70 @@
-
-
+
+
+
+ Show messages from a specific
+ boot. This will add a match for
+ _BOOT_ID=.
+
+ 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.
+
- Show data only from
- current boot. This will add a match
- for _BOOT_ID= for
- the current boot ID of the
- kernel.
+
+
+
+
+
+
+ Show a tabular list of
+ boot numbers (relative to current
+ boot), their IDs, and the timestamps
+ of the first and last message
+ pertaining to the boot.
+
- Show kernel messages from
- current boot. This implies
- and adds the match _TRANSPORT=kernel.
+ Show only kernel messages. This
+ implies and adds the match
+ _TRANSPORT=kernel.
@@ -422,6 +582,16 @@
cursor.
+
+
+
+ Start showing entries from the
+ location in the journal
+ after the location
+ specified by the this cursor.
+
+
+
@@ -721,6 +891,10 @@
journalctl /dev/sda
+ Show all kernel logs from previous boot:
+
+ journalctl -k -b -1
+