X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fjournalctl.xml;h=959ae1efa271c2422829874a9aa4b675bf387396;hb=7e2c2bcf1285d124c9c656ff46cafa4db0a987c9;hp=3cfda5b84b5fbf12c92a79012760bb7469389d13;hpb=b6a345143bf6ffdc87a7149015f75c03be440b10;p=elogind.git
diff --git a/man/journalctl.xml b/man/journalctl.xml
index 3cfda5b84..959ae1efa 100644
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -62,7 +62,7 @@
journal as written by
systemd-journald.service8.
- If called without parameter will show the full
+ If called without parameter it will show the full
contents of the journal, starting with the oldest
entry collected.
@@ -135,6 +135,13 @@
pager.
+
+
+
+ Show all (printable) fields in
+ full.
+
+
@@ -149,7 +156,7 @@
- Show only most recent
+ Show only the most recent
journal entries, and continuously print
new entries as they are appended to
the journal.
@@ -159,13 +166,13 @@
- Controls the number of
- journal lines to show, counting from
- the most recent ones. Takes a positive
- integer argument. In follow mode
- defaults to 10, otherwise is unset
- thus not limiting how many lines are
- shown.
+ Show the most recent
+ journal events and limit the number of
+ events shown. If
+ is used,
+ this option is implied. The argument,
+ a positive integer, is optional, and
+ defaults to 10.
@@ -189,6 +196,8 @@
verbose,
export,
json,
+ json-pretty,
+ json-sse,
cat. short
is the default and generates an output
that is mostly identical to the
@@ -209,13 +218,51 @@
Export Format for more
information). json
formats entries as JSON data
- structures. cat
+ 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.
+
+
+
+
+ Augment log lines with
+ explanation texts from the message
+ catalog. This will add explanatory
+ help texts to log messages in the
+ output where this is available. These
+ short help texts will explain the
+ context of an error or log event,
+ possible solutions, as well as
+ pointers to support forums, developer
+ documentation and any other relevant
+ manuals. Note that help texts are not
+ available for all messages, but only
+ for selected ones. For more
+ information on the message catalog
+ please refer to the Message
+ Catalog Developer
+ Documentation.
+
+
@@ -227,11 +274,13 @@
-
-
+
+
- Show only locally
- generated messages.
+ Show entries
+ interleaved from all available
+ journals, including remote
+ ones.
@@ -239,7 +288,106 @@
Show data only from
- current boot.
+ current boot. This will add a match
+ for _BOOT_ID= for
+ the current boot ID of the
+ kernel.
+
+
+
+
+
+
+ Show data only of the
+ specified unit. This will add a match
+ for _SYSTEMD_UNIT=
+ for the specified
+ unit.
+
+
+
+
+
+
+ Filter output by
+ message priorities or priority
+ ranges. Takes either a single numeric
+ or textual log level (i.e. between
+ 0/emerg and
+ 7/debug), or a
+ range of numeric/text log levels in
+ the form FROM..TO. The log levels are
+ the usual syslog log levels as
+ documented in
+ syslog3,
+ i.e. emerg (0),
+ alert (1),
+ crit (2),
+ err (3),
+ warning (4),
+ notice (5),
+ info (6),
+ debug (7). If a
+ single log level is specified all
+ messages with this log level or a
+ lower (hence more important) log level
+ are shown. If a range is specified all
+ messages within the range are shown,
+ including both the start and the end
+ value of the range. This will add
+ PRIORITY= matches
+ for the specified
+ priorities.
+
+
+
+
+
+
+ Start showing entries
+ from the location in the journal
+ specified by the passed
+ cursor.
+
+
+
+
+
+
+ Start showing entries
+ on or newer than the specified date,
+ or on or older than the specified
+ date, respectively. Date specifications should be of
+ the format "2012-10-30 18:17:16". If
+ the time part is omitted, 00:00:00 is
+ assumed. If only the seconds component
+ is omitted, :00 is assumed. If the
+ date component is omitted, the
+ current day is assumed. Alternatively
+ the strings
+ yesterday,
+ today,
+ tomorrow are
+ understood, which refer to 00:00:00 of
+ the day before the current day, the
+ current day, or the day after the
+ current day, respectively. now
+ refers to the current time. Finally,
+ relative times may be specified,
+ prefixed with - or
+ +, referring to
+ times before or after the current
+ time, respectively.
+
+
+
+
+
+
+ Print all possible
+ data values the specified field can
+ take in all entries of the
+ journal.
@@ -248,7 +396,7 @@
Takes an absolute
directory path as argument. If
- specified will operate on the
+ specified journalctl will operate on the
specified journal directory instead of
the default runtime and system journal
paths.
@@ -275,40 +423,86 @@
Instead of showing
journal contents show internal header
- information of the journal fiels
+ information of the journal fields
accessed.
-
-
+
- Filter output by
- message priorities or priority
- ranges. Takes either a single numeric
- or textual log level (i.e. between
- 0/emerg and
- 7/debug), or a
- range of numeric/text log levels in
- the form FROM..TO. The log levels are
- the usual syslog log levels as
- documented in
- syslog3,
- i.e. emerg (0),
- alert (1),
- crit (2),
- err (3),
- warning (4),
- notice (5),
- info (6),
- debug (7). If a
- single log level is specified all
- messages with this log levels or a
- lower (hence more important) log level
- are shown. If a range is specified all
- messages within the range are shown,
- including both the start and the end
- value of the range.
+ Shows the current disk
+ usage of all
+ journal files.
+
+
+
+
+
+ List the contents of
+ the message catalog, as table of
+ message IDs plus their short
+ description strings.
+
+
+
+
+
+ Update the message
+ catalog index. This command needs to
+ be executed each time new catalog
+ files are installed, removed or
+ updated to rebuild the binary catalog
+ index.
+
+
+
+
+
+ Instead of showing
+ journal contents generate a new key
+ pair for Forward Secure Sealing
+ (FSS). This will generate a sealing
+ key and a verification key. The
+ sealing key is stored in the journal
+ data directory and shall remain on the
+ host. The verification key should be
+ stored externally.
+
+
+
+
+
+ Specifies the change
+ interval for the sealing key, when
+ generating an FSS key pair with
+ . Shorter
+ intervals increase CPU consumption but
+ shorten the time range of
+ undetectable journal
+ alterations. Defaults to
+ 15min.
+
+
+
+
+
+ Check the journal file
+ for internal consistency. If the
+ file has been generated with FSS
+ enabled, and the FSS verification key
+ has been specified with
+
+ authenticity of the journal file is
+ verified.
+
+
+
+
+
+ Specifies the FSS
+ verification key to use for the
+
+ operation.
@@ -358,7 +552,7 @@
journalctl _SYSTEMD_UNIT=avahi-daemon.service _SYSTEMD_UNIT=dbus.serviceIf the separator "+" is used
- two expression may be combined in a logical OR. The
+ two expressions may be combined in a logical OR. The
following will show all messages from the Avahi
service process with the PID 28097 plus all messages
from the D-Bus service (from any of its