X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fjournalctl.xml;h=2de72523ccc51da35f18a703d0385eb2e9cb1f27;hb=565a9388f261c6e459e1726e358284ff687ec941;hp=71b1babb10f818ac285ecbba6eea114be504bd01;hpb=b8547c10c82994f2b8eab4510629139439b49371;p=elogind.git
diff --git a/man/journalctl.xml b/man/journalctl.xml
index 71b1babb1..2de72523c 100644
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -84,7 +84,7 @@
alternatives, i.e. the resulting output will show
entries matching any of the specified matches for the
same field. Finally, if the character
- + appears as separate word on the
+ + appears as a separate word on the
command line, all matches before and after are combined
in a disjunction (i.e. logical OR).
@@ -104,9 +104,23 @@
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.
+
+ The output is paged through
+ less by default, and long lines are
+ "truncated" to screen width. The hidden part can be
+ viewed by using the left-arrow and right-arrow
+ keys. Paging can be disabled; see the
+ option and the "Environment"
+ section below.
+
+ When outputing to a tty, lines are colored
+ according to priority: lines of level ERROR and higher
+ are colored red; lines of level NOTICE and higher are
+ highlighted; and other lines are displayed normally.
+
@@ -138,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
+ .
@@ -209,7 +232,7 @@
- Reverse output, so the newest
+ Reverse output so the newest
entries are displayed first.
@@ -219,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 by 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.
+
+
+
+
+
@@ -281,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
@@ -289,7 +409,14 @@
please refer to the Message
Catalog Developer
- Documentation.
+ Documentation.
+
+ Note: when attaching
+ journalctl output
+ to bug reports, please do
+ not use
+ .
+
@@ -297,8 +424,8 @@
Suppresses any warning
- message regarding inaccessible system
- journals when run as normal
+ messages regarding inaccessible system
+ journals when run as a normal
user.
@@ -313,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
+ chronological order, 2 the
+ second and so on; while -0
+ is the last boot, -1 the
+ boot before last, 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 the 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.
@@ -408,6 +582,28 @@
cursor.
+
+
+
+ Start showing entries
+ from the location in the journal
+ after the
+ location specified by the this cursor.
+ The cursor is shown when the
+ option
+ is used.
+
+
+
+
+
+ The cursor is shown after the last
+ entry after two dashes:
+ -- cursor: s=0639...
+ The format of the cursor is private
+ and subject to change.
+
+
@@ -455,7 +651,7 @@
Show messages from
system services and the kernel (with
- ). Show
+ ). Show
messages from service of current user
(with ).
If neither is specified, show all
@@ -463,6 +659,16 @@
+
+
+
+
+ Show messages from a
+ running, local container. Specify a
+ container name to connect
+ to.
+
+
@@ -479,13 +685,13 @@
- Takes a file glob as
+ Takes a file glob as an
argument. If specified, journalctl will
operate on the specified journal files
matching GLOB
instead of the default runtime and
system journal paths. May be specified
- multiple times, in which case files will
+ multiple times, in which case, files will
be suitably interleaved.
@@ -493,7 +699,7 @@
Takes a directory path
- as argument. If specified, journalctl
+ as an argument. If specified, journalctl
will operate on catalog file hierarchy
underneath the specified directory
instead of the root directory
@@ -507,8 +713,8 @@
Instead of showing
- journal contents, generate a new 128
- bit ID suitable for identifying
+ journal contents, generate a new 128-bit
+ ID suitable for identifying
messages. This is intended for usage
by developers who need a new
identifier for a new message they
@@ -538,16 +744,16 @@
List the contents of
- the message catalog, as table of
- message IDs plus their short
+ the message catalog as a table of
+ message IDs, plus their short
description strings.If any
- ID128s are
+ 128-bit-IDs are
specified, only those entries are shown.
@@ -555,18 +761,18 @@
Show the contents of
the message catalog, with entries
separated by a line consisting of two
- dashes and the id (the format is the
+ dashes and the ID (the format is the
same as .catalog
- files.
+ files).If any
- ID128s are
+ 128-bit-IDs are
specified, only those entries are shown.
@@ -578,7 +784,7 @@
Update the message
catalog index. This command needs to
be executed each time new catalog
- files are installed, removed or
+ files are installed, removed, or
updated to rebuild the binary catalog
index.
@@ -594,18 +800,23 @@
sealing key is stored in the journal
data directory and shall remain on the
host. The verification key should be
- stored externally. Also see the
+ stored externally. Refer to the
option in
journald.conf5
- for details.
+ for information on Forward Secure
+ Sealing and for a link to a refereed
+ scholarly paper detailing the
+ cryptographic theory it is based on.
+
- When --setup-keys is passed and
- Forward Secure Sealing has already been set up,
- recreate FSS keys.
+ When
+ is passed and
+ Forward Secure Sealing (FSS) has already been
+ configured, recreate FSS keys.
@@ -650,8 +861,8 @@
Exit status
- On success, 0 is returned, a non-zero failure
- code otherwise.
+ On success, 0 is returned; otherwise, a non-zero
+ failure code is returned.
@@ -707,6 +918,10 @@
journalctl /dev/sda
+ Show all kernel logs from previous boot:
+
+ journalctl -k -b -1
+