1 <?xml version='
1.0'
?> <!--*-nxml-*-->
2 <!DOCTYPE refentry PUBLIC
"-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
6 This file is part of systemd.
8 Copyright 2012 Lennart Poettering
10 systemd is free software; you can redistribute it and/or modify it
11 under the terms of the GNU Lesser General Public License as published by
12 the Free Software Foundation; either version 2.1 of the License, or
13 (at your option) any later version.
15 systemd is distributed in the hope that it will be useful, but
16 WITHOUT ANY WARRANTY; without even the implied warranty of
17 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
18 Lesser General Public License for more details.
20 You should have received a copy of the GNU Lesser General Public License
21 along with systemd; If not, see <http://www.gnu.org/licenses/>.
24 <refentry id=
"journalctl"
25 xmlns:
xi=
"http://www.w3.org/2001/XInclude">
28 <title>journalctl
</title>
29 <productname>systemd
</productname>
33 <contrib>Developer
</contrib>
34 <firstname>Lennart
</firstname>
35 <surname>Poettering
</surname>
36 <email>lennart@poettering.net
</email>
42 <refentrytitle>journalctl
</refentrytitle>
43 <manvolnum>1</manvolnum>
47 <refname>journalctl
</refname>
48 <refpurpose>Query the systemd journal
</refpurpose>
53 <command>journalctl
</command>
54 <arg choice=
"opt" rep=
"repeat">OPTIONS
</arg>
55 <arg choice=
"opt" rep=
"repeat">MATCHES
</arg>
60 <title>Description
</title>
62 <para><command>journalctl
</command> may be used to query the
64 <citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
66 <citerefentry><refentrytitle>systemd-journald.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
68 <para>If called without parameters, it will show the full
69 contents of the journal, starting with the oldest entry
72 <para>If one or more match arguments are passed, the output is
73 filtered accordingly. A match is in the format
74 <literal>FIELD=VALUE
</literal>,
75 e.g.
<literal>_SYSTEMD_UNIT=httpd.service
</literal>, referring
76 to the components of a structured journal entry. See
77 <citerefentry><refentrytitle>systemd.journal-fields
</refentrytitle><manvolnum>7</manvolnum></citerefentry>
78 for a list of well-known fields. If multiple matches are
79 specified matching different fields, the log entries are
80 filtered by both, i.e. the resulting output will show only
81 entries matching all the specified matches of this kind. If two
82 matches apply to the same field, then they are automatically
83 matched as alternatives, i.e. the resulting output will show
84 entries matching any of the specified matches for the same
85 field. Finally, the character
<literal>+
</literal> may appear
86 as a separate word between other terms on the command line. This
87 causes all matches before and after to be combined in a
88 disjunction (i.e. logical OR).
</para>
90 <para>It is also possible to filter the entries by specifying an
91 absolute file path as an argument. The file path may be a file or
92 a symbolic link and the file must exist at the time of the query. If a
93 file path refers to an executable binary, an
<literal>_EXE=
</literal>
94 match for the canonicalized binary path is added to the query. If a
95 file path refers to an executable script, a
<literal>_COMM=
</literal>
96 match for the script name is added to the query. If a file path
97 refers to a device node,
<literal>_KERNEL_DEVICE=
</literal> matches for
98 the kernel name of the device and for each of its ancestor devices is
99 added to the query. Symbolic links are dereferenced, kernel names are
100 synthesized, and parent devices are identified from the environment at
101 the time of the query. In general, a device node is the best proxy for
102 an actual device, as log entries do not usually contain fields that
103 identify an actual device. For the resulting log entries to be correct
104 for the actual device, the relevant parts of the environment at the time
105 the entry was logged, in particular the actual device corresponding to
106 the device node, must have been the same as those at the time of the
107 query. Because device nodes generally change their corresponding devices
108 across reboots, specifying a device node path causes the resulting
109 entries to be restricted to those from the current boot.
</para>
111 <para>Additional constraints may be added using options
112 <option>--boot
</option>,
<option>--unit=
</option>, etc., to
113 further limit what entries will be shown (logical AND).
</para>
115 <para>Output is interleaved from all accessible journal files,
116 whether they are rotated or currently being written, and
117 regardless of whether they belong to the system itself or are
118 accessible user journals.
</para>
120 <para>The set of journal files which will be used can be
121 modified using the
<option>--user
</option>,
122 <option>--system
</option>,
<option>--directory
</option>, and
123 <option>--file
</option> options, see below.
</para>
125 <para>All users are granted access to their private per-user
126 journals. However, by default, only root and users who are
127 members of a few special groups are granted access to the system
128 journal and the journals of other users. Members of the groups
129 <literal>systemd-journal
</literal>,
<literal>adm
</literal>, and
130 <literal>wheel
</literal> can read all journal files. Note
131 that the two latter groups traditionally have additional
132 privileges specified by the distribution. Members of the
133 <literal>wheel
</literal> group can often perform administrative
136 <para>The output is paged through
<command>less
</command> by
137 default, and long lines are
"truncated" to screen width. The
138 hidden part can be viewed by using the left-arrow and
139 right-arrow keys. Paging can be disabled; see the
140 <option>--no-pager
</option> option and the
"Environment" section
143 <para>When outputting to a tty, lines are colored according to
144 priority: lines of level ERROR and higher are colored red; lines
145 of level NOTICE and higher are highlighted; other lines are
146 displayed normally.
</para>
150 <title>Options
</title>
152 <para>The following options are understood:
</para>
156 <term><option>--no-full
</option></term>
157 <term><option>--full
</option></term>
158 <term><option>-l
</option></term>
160 <listitem><para>Ellipsize fields when they do not fit in
161 available columns. The default is to show full fields,
162 allowing them to wrap or be truncated by the pager, if one
165 <para>The old options
166 <option>-l
</option>/
<option>--full
</option> are not useful
167 anymore, except to undo
<option>--no-full
</option>.
</para>
172 <term><option>-a
</option></term>
173 <term><option>--all
</option></term>
175 <listitem><para>Show all fields in full, even if they
176 include unprintable characters or are very
177 long.
</para></listitem>
181 <term><option>-f
</option></term>
182 <term><option>--follow
</option></term>
184 <listitem><para>Show only the most recent journal entries,
185 and continuously print new entries as they are appended to
186 the journal.
</para></listitem>
190 <term><option>-e
</option></term>
191 <term><option>--pager-end
</option></term>
193 <listitem><para>Immediately jump to the end of the journal
194 inside the implied pager tool. This implies
195 <option>-n1000
</option> to guarantee that the pager will not
196 buffer logs of unbounded size. This may be overridden with
197 an explicit
<option>-n
</option> with some other numeric
198 value, while
<option>-nall
</option> will disable this cap.
199 Note that this option is only supported for the
200 <citerefentry project='man-pages'
><refentrytitle>less
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
201 pager.
</para></listitem>
205 <term><option>-n
</option></term>
206 <term><option>--lines=
</option></term>
208 <listitem><para>Show the most recent journal events and
209 limit the number of events shown. If
210 <option>--follow
</option> is used, this option is
211 implied. The argument is a positive integer or
212 <literal>all
</literal> to disable line limiting. The default
213 value is
10 if no argument is given.
</para></listitem>
217 <term><option>--no-tail
</option></term>
219 <listitem><para>Show all stored output lines, even in follow
220 mode. Undoes the effect of
<option>--lines=
</option>.
225 <term><option>-r
</option></term>
226 <term><option>--reverse
</option></term>
228 <listitem><para>Reverse output so that the newest entries
229 are displayed first.
</para></listitem>
233 <term><option>-o
</option></term>
234 <term><option>--output=
</option></term>
236 <listitem><para>Controls the formatting of the journal
237 entries that are shown. Takes one of the following
242 <option>short
</option>
245 <para>is the default and generates an output that is
246 mostly identical to the formatting of classic syslog
247 files, showing one line per journal entry.
</para>
253 <option>short-full
</option>
256 <para>is very similar, but shows timestamps in the format the
<option>--since=
</option> and
257 <option>--until=
</option> options accept. Unlike the timestamp information shown in
258 <option>short
</option> output mode this mode includes weekday, year and timezone information in the
259 output, and is locale-independent.
</para>
265 <option>short-iso
</option>
268 <para>is very similar, but shows ISO
8601 wallclock
275 <option>short-iso-precise
</option>
278 <para>as for
<option>short-iso
</option> but includes full
279 microsecond precision.
</para>
285 <option>short-precise
</option>
288 <para>is very similar, but shows classic syslog timestamps
289 with full microsecond precision.
</para>
295 <option>short-monotonic
</option>
298 <para>is very similar, but shows monotonic timestamps
299 instead of wallclock timestamps.
</para>
305 <option>short-unix
</option>
308 <para>is very similar, but shows seconds passed since January
1st
1970 UTC instead of wallclock
309 timestamps (
"UNIX time"). The time is shown with microsecond accuracy.
</para>
315 <option>verbose
</option>
318 <para>shows the full-structured entry items with all
325 <option>export
</option>
328 <para>serializes the journal into a binary (but mostly
329 text-based) stream suitable for backups and network
331 <ulink url=
"https://www.freedesktop.org/wiki/Software/systemd/export">Journal Export Format
</ulink>
332 for more information). To import the binary stream back
333 into native journald format use
334 <citerefentry><refentrytitle>systemd-journal-remote
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
340 <option>json
</option>
343 <para>formats entries as JSON data structures, one per
345 <ulink url=
"https://www.freedesktop.org/wiki/Software/systemd/json">Journal JSON Format
</ulink>
346 for more information).
</para>
352 <option>json-pretty
</option>
355 <para>formats entries as JSON data structures, but
356 formats them in multiple lines in order to make them
357 more readable by humans.
</para>
363 <option>json-sse
</option>
366 <para>formats entries as JSON data structures, but wraps
367 them in a format suitable for
368 <ulink url=
"https://developer.mozilla.org/en-US/docs/Server-sent_events/Using_server-sent_events">Server-Sent Events
</ulink>.
378 <para>generates a very terse output, only showing the
379 actual message of each journal entry with no metadata,
380 not even a timestamp.
</para>
388 <term><option>--utc
</option></term>
390 <listitem><para>Express time in Coordinated Universal Time
391 (UTC).
</para></listitem>
395 <term><option>--no-hostname
</option></term>
397 <listitem><para>Don't show the hostname field of log messages originating from the local host. This switch only
398 has an effect on the
<option>short
</option> family of output modes (see above).
</para></listitem>
402 <term><option>-x
</option></term>
403 <term><option>--catalog
</option></term>
405 <listitem><para>Augment log lines with explanation texts from
406 the message catalog. This will add explanatory help texts to
407 log messages in the output where this is available. These
408 short help texts will explain the context of an error or log
409 event, possible solutions, as well as pointers to support
410 forums, developer documentation, and any other relevant
411 manuals. Note that help texts are not available for all
412 messages, but only for selected ones. For more information on
413 the message catalog, please refer to the
414 <ulink url=
"https://www.freedesktop.org/wiki/Software/systemd/catalog">Message Catalog Developer Documentation
</ulink>.
</para>
416 <para>Note: when attaching
<command>journalctl
</command>
417 output to bug reports, please do
<emphasis>not
</emphasis> use
418 <option>-x
</option>.
</para>
423 <term><option>-q
</option></term>
424 <term><option>--quiet
</option></term>
426 <listitem><para>Suppresses all info messages
427 (i.e.
"-- Logs begin at …",
"-- Reboot --"),
428 any warning messages regarding
429 inaccessible system journals when run as a normal
430 user.
</para></listitem>
434 <term><option>-m
</option></term>
435 <term><option>--merge
</option></term>
437 <listitem><para>Show entries interleaved from all available
438 journals, including remote ones.
</para></listitem>
442 <term><option>-b
<optional><replaceable>ID
</replaceable></optional><optional><replaceable>±offset
</replaceable></optional></option></term>
443 <term><option>--boot=
<optional><replaceable>ID
</replaceable></optional><optional><replaceable>±offset
</replaceable></optional></option></term>
445 <listitem><para>Show messages from a specific boot. This will
446 add a match for
<literal>_BOOT_ID=
</literal>.
</para>
448 <para>The argument may be empty, in which case logs for the
449 current boot will be shown.
</para>
451 <para>If the boot ID is omitted, a positive
452 <replaceable>offset
</replaceable> will look up the boots
453 starting from the beginning of the journal, and an
454 equal-or-less-than zero
<replaceable>offset
</replaceable> will
455 look up boots starting from the end of the journal. Thus,
456 <constant>1</constant> means the first boot found in the
457 journal in chronological order,
<constant>2</constant> the
458 second and so on; while
<constant>-
0</constant> is the last
459 boot,
<constant>-
1</constant> the boot before last, and so
460 on. An empty
<replaceable>offset
</replaceable> is equivalent
461 to specifying
<constant>-
0</constant>, except when the current
462 boot is not the last boot (e.g. because
463 <option>--directory
</option> was specified to look at logs
464 from a different machine).
</para>
466 <para>If the
32-character
<replaceable>ID
</replaceable> is
467 specified, it may optionally be followed by
468 <replaceable>offset
</replaceable> which identifies the boot
469 relative to the one given by boot
470 <replaceable>ID
</replaceable>. Negative values mean earlier
471 boots and positive values mean later boots. If
472 <replaceable>offset
</replaceable> is not specified, a value of
473 zero is assumed, and the logs for the boot given by
474 <replaceable>ID
</replaceable> are shown.
</para>
479 <term><option>--list-boots
</option></term>
481 <listitem><para>Show a tabular list of boot numbers (relative to
482 the current boot), their IDs, and the timestamps of the first
483 and last message pertaining to the boot.
</para></listitem>
487 <term><option>-k
</option></term>
488 <term><option>--dmesg
</option></term>
490 <listitem><para>Show only kernel messages. This implies
491 <option>-b
</option> and adds the match
492 <literal>_TRANSPORT=kernel
</literal>.
</para></listitem>
496 <term><option>-t
</option></term>
497 <term><option>--identifier=
<replaceable>SYSLOG_IDENTIFIER
</replaceable></option></term>
499 <listitem><para>Show messages for the specified syslog
501 <replaceable>SYSLOG_IDENTIFIER
</replaceable>.
</para>
503 <para>This parameter can be specified multiple
504 times.
</para></listitem>
508 <term><option>-u
</option></term>
509 <term><option>--unit=
<replaceable>UNIT
</replaceable>|
<replaceable>PATTERN
</replaceable></option></term>
511 <listitem><para>Show messages for the specified systemd unit
512 <replaceable>UNIT
</replaceable> (such as a service unit), or
513 for any of the units matched by
514 <replaceable>PATTERN
</replaceable>. If a pattern is
515 specified, a list of unit names found in the journal is
516 compared with the specified pattern and all that match are
517 used. For each unit name, a match is added for messages from
519 (
<literal>_SYSTEMD_UNIT=
<replaceable>UNIT
</replaceable></literal>),
520 along with additional matches for messages from systemd and
521 messages about coredumps for the specified unit.
</para>
523 <para>This parameter can be specified multiple times.
</para>
528 <term><option>--user-unit=
</option></term>
530 <listitem><para>Show messages for the specified user session
531 unit. This will add a match for messages from the unit
532 (
<literal>_SYSTEMD_USER_UNIT=
</literal> and
533 <literal>_UID=
</literal>) and additional matches for messages
534 from session systemd and messages about coredumps for the
535 specified unit.
</para>
537 <para>This parameter can be specified multiple times.
</para>
542 <term><option>-p
</option></term>
543 <term><option>--priority=
</option></term>
545 <listitem><para>Filter output by message priorities or
546 priority ranges. Takes either a single numeric or textual log
547 level (i.e. between
0/
<literal>emerg
</literal> and
548 7/
<literal>debug
</literal>), or a range of numeric/text log
549 levels in the form FROM..TO. The log levels are the usual
550 syslog log levels as documented in
551 <citerefentry project='man-pages'
><refentrytitle>syslog
</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
552 i.e.
<literal>emerg
</literal> (
0),
553 <literal>alert
</literal> (
1),
<literal>crit
</literal> (
2),
554 <literal>err
</literal> (
3),
<literal>warning
</literal> (
4),
555 <literal>notice
</literal> (
5),
<literal>info
</literal> (
6),
556 <literal>debug
</literal> (
7). If a single log level is
557 specified, all messages with this log level or a lower (hence
558 more important) log level are shown. If a range is specified,
559 all messages within the range are shown, including both the
560 start and the end value of the range. This will add
561 <literal>PRIORITY=
</literal> matches for the specified
562 priorities.
</para></listitem>
566 <term><option>-c
</option></term>
567 <term><option>--cursor=
</option></term>
569 <listitem><para>Start showing entries from the location in the
570 journal specified by the passed cursor.
</para></listitem>
574 <term><option>--after-cursor=
</option></term>
576 <listitem><para>Start showing entries from the location in the
577 journal
<emphasis>after
</emphasis> the location specified by
578 the passed cursor. The cursor is shown when the
579 <option>--show-cursor
</option> option is used.
</para>
584 <term><option>--show-cursor
</option></term>
586 <listitem><para>The cursor is shown after the last entry after
588 <programlisting>-- cursor: s=
0639…
</programlisting>
589 <para>The format of the cursor is private
590 and subject to change.
</para></listitem>
594 <term><option>-S
</option></term>
595 <term><option>--since=
</option></term>
596 <term><option>-U
</option></term>
597 <term><option>--until=
</option></term>
599 <listitem><para>Start showing entries on or newer than the specified date, or on or older than the specified
600 date, respectively. Date specifications should be of the format
<literal>2012-
10-
30 18:
17:
16</literal>. If the
601 time part is omitted,
<literal>00:
00:
00</literal> is assumed. If only the seconds component is omitted,
602 <literal>:
00</literal> is assumed. If the date component is omitted, the current day is assumed. Alternatively
603 the strings
<literal>yesterday
</literal>,
<literal>today
</literal>,
<literal>tomorrow
</literal> are understood,
604 which refer to
00:
00:
00 of the day before the current day, the current day, or the day after the current day,
605 respectively.
<literal>now
</literal> refers to the current time. Finally, relative times may be specified,
606 prefixed with
<literal>-
</literal> or
<literal>+
</literal>, referring to times before or after the current
607 time, respectively. For complete time and date specification, see
608 <citerefentry><refentrytitle>systemd.time
</refentrytitle><manvolnum>7</manvolnum></citerefentry>. Note that
609 <option>--output=short-full
</option> prints timestamps that follow precisely this format.
615 <term><option>-F
</option></term>
616 <term><option>--field=
</option></term>
618 <listitem><para>Print all possible data values the specified
619 field can take in all entries of the journal.
</para></listitem>
623 <term><option>-N
</option></term>
624 <term><option>--fields
</option></term>
626 <listitem><para>Print all field names currently used in all entries of the journal.
</para></listitem>
630 <term><option>--system
</option></term>
631 <term><option>--user
</option></term>
633 <listitem><para>Show messages from system services and the
634 kernel (with
<option>--system
</option>). Show messages from
635 service of current user (with
<option>--user
</option>). If
636 neither is specified, show all messages that the user can see.
641 <term><option>-M
</option></term>
642 <term><option>--machine=
</option></term>
644 <listitem><para>Show messages from a running, local
645 container. Specify a container name to connect to.
</para>
650 <term><option>-D
<replaceable>DIR
</replaceable></option></term>
651 <term><option>--directory=
<replaceable>DIR
</replaceable></option></term>
653 <listitem><para>Takes a directory path as argument. If
654 specified, journalctl will operate on the specified journal
655 directory
<replaceable>DIR
</replaceable> instead of the
656 default runtime and system journal paths.
</para></listitem>
660 <term><option>--file=
<replaceable>GLOB
</replaceable></option></term>
662 <listitem><para>Takes a file glob as an argument. If
663 specified, journalctl will operate on the specified journal
664 files matching
<replaceable>GLOB
</replaceable> instead of the
665 default runtime and system journal paths. May be specified
666 multiple times, in which case files will be suitably
667 interleaved.
</para></listitem>
671 <term><option>--root=
<replaceable>ROOT
</replaceable></option></term>
673 <listitem><para>Takes a directory path as an argument. If
674 specified, journalctl will operate on journal directories and catalog file hierarchy
675 underneath the specified directory instead of the root
676 directory (e.g.
<option>--update-catalog
</option> will create
677 <filename><replaceable>ROOT
</replaceable>/var/lib/systemd/catalog/database
</filename>,
678 and journal files under
<filename><replaceable>ROOT
</replaceable>/run/journal
</filename>
679 or
<filename><replaceable>ROOT
</replaceable>/var/log/journal
</filename> will be displayed).
684 <term><option>--new-id128
</option></term>
686 <listitem><para>Instead of showing journal contents, generate
687 a new
128-bit ID suitable for identifying messages. This is
688 intended for usage by developers who need a new identifier for
689 a new message they introduce and want to make
690 recognizable. This will print the new ID in four different
691 formats which can be copied into source code or similar.
696 <term><option>--header
</option></term>
698 <listitem><para>Instead of showing journal contents, show
699 internal header information of the journal fields
700 accessed.
</para></listitem>
704 <term><option>--disk-usage
</option></term>
706 <listitem><para>Shows the current disk usage of all journal
707 files. This shows the sum of the disk usage of all archived
708 and active journal files.
</para></listitem>
712 <term><option>--vacuum-size=
</option></term>
713 <term><option>--vacuum-time=
</option></term>
714 <term><option>--vacuum-files=
</option></term>
716 <listitem><para>Removes archived journal files until the disk
717 space they use falls below the specified size (specified with
718 the usual
<literal>K
</literal>,
<literal>M
</literal>,
719 <literal>G
</literal> and
<literal>T
</literal> suffixes), or all
720 archived journal files contain no data older than the specified
721 timespan (specified with the usual
<literal>s
</literal>,
722 <literal>m
</literal>,
<literal>h
</literal>,
723 <literal>days
</literal>,
<literal>months
</literal>,
724 <literal>weeks
</literal> and
<literal>years
</literal> suffixes),
725 or no more than the specified number of separate journal files
726 remain. Note that running
<option>--vacuum-size=
</option> has
727 only an indirect effect on the output shown by
728 <option>--disk-usage
</option>, as the latter includes active
729 journal files, while the vacuuming operation only operates
730 on archived journal files. Similarly,
731 <option>--vacuum-files=
</option> might not actually reduce the
732 number of journal files to below the specified number, as it
733 will not remove active journal
734 files.
<option>--vacuum-size=
</option>,
735 <option>--vacuum-time=
</option> and
736 <option>--vacuum-files=
</option> may be combined in a single
737 invocation to enforce any combination of a size, a time and a
738 number of files limit on the archived journal
739 files. Specifying any of these three parameters as zero is
740 equivalent to not enforcing the specific limit, and is thus
741 redundant.
</para></listitem>
745 <term><option>--list-catalog
746 <optional><replaceable>128-bit-ID…
</replaceable></optional>
749 <listitem><para>List the contents of the message catalog as a
750 table of message IDs, plus their short description strings.
753 <para>If any
<replaceable>128-bit-ID
</replaceable>s are
754 specified, only those entries are shown.
</para>
759 <term><option>--dump-catalog
760 <optional><replaceable>128-bit-ID…
</replaceable></optional>
763 <listitem><para>Show the contents of the message catalog, with
764 entries separated by a line consisting of two dashes and the
765 ID (the format is the same as
<filename>.catalog
</filename>
768 <para>If any
<replaceable>128-bit-ID
</replaceable>s are
769 specified, only those entries are shown.
</para>
774 <term><option>--update-catalog
</option></term>
776 <listitem><para>Update the message catalog index. This command
777 needs to be executed each time new catalog files are
778 installed, removed, or updated to rebuild the binary catalog
779 index.
</para></listitem>
783 <term><option>--setup-keys
</option></term>
785 <listitem><para>Instead of showing journal contents, generate
786 a new key pair for Forward Secure Sealing (FSS). This will
787 generate a sealing key and a verification key. The sealing key
788 is stored in the journal data directory and shall remain on
789 the host. The verification key should be stored
790 externally. Refer to the
<option>Seal=
</option> option in
791 <citerefentry><refentrytitle>journald.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
792 for information on Forward Secure Sealing and for a link to a
793 refereed scholarly paper detailing the cryptographic theory it
794 is based on.
</para></listitem>
798 <term><option>--force
</option></term>
800 <listitem><para>When
<option>--setup-keys
</option> is passed
801 and Forward Secure Sealing (FSS) has already been configured,
802 recreate FSS keys.
</para></listitem>
806 <term><option>--interval=
</option></term>
808 <listitem><para>Specifies the change interval for the sealing
809 key when generating an FSS key pair with
810 <option>--setup-keys
</option>. Shorter intervals increase CPU
811 consumption but shorten the time range of undetectable journal
812 alterations. Defaults to
15min.
</para></listitem>
816 <term><option>--verify
</option></term>
818 <listitem><para>Check the journal file for internal
819 consistency. If the file has been generated with FSS enabled and
820 the FSS verification key has been specified with
821 <option>--verify-key=
</option>, authenticity of the journal file
822 is verified.
</para></listitem>
826 <term><option>--verify-key=
</option></term>
828 <listitem><para>Specifies the FSS verification key to use for
829 the
<option>--verify
</option> operation.
</para></listitem>
833 <term><option>--sync
</option></term>
835 <listitem><para>Asks the journal daemon to write all yet
836 unwritten journal data to the backing file system and
837 synchronize all journals. This call does not return until the
838 synchronization operation is complete. This command guarantees
839 that any log messages written before its invocation are safely
840 stored on disk at the time it returns.
</para></listitem>
844 <term><option>--flush
</option></term>
846 <listitem><para>Asks the journal daemon to flush any log data
847 stored in
<filename>/run/log/journal
</filename> into
848 <filename>/var/log/journal
</filename>, if persistent storage
849 is enabled. This call does not return until the operation is
850 complete. Note that this call is idempotent: the data is only
851 flushed from
<filename>/run/log/journal
</filename> into
852 <filename>/var/log/journal
</filename> once during system
853 runtime, and this command exits cleanly without executing any
854 operation if this has already happened. This command
855 effectively guarantees that all data is flushed to
856 <filename>/var/log/journal
</filename> at the time it
857 returns.
</para></listitem>
861 <term><option>--rotate
</option></term>
863 <listitem><para>Asks the journal daemon to rotate journal
864 files. This call does not return until the rotation operation
865 is complete.
</para></listitem>
868 <xi:include href=
"standard-options.xml" xpointer=
"help" />
869 <xi:include href=
"standard-options.xml" xpointer=
"version" />
870 <xi:include href=
"standard-options.xml" xpointer=
"no-pager" />
875 <title>Exit status
</title>
877 <para>On success,
0 is returned; otherwise, a non-zero failure
878 code is returned.
</para>
881 <xi:include href=
"less-variables.xml" />
884 <title>Examples
</title>
886 <para>Without arguments, all collected logs are shown
889 <programlisting>journalctl
</programlisting>
891 <para>With one match specified, all entries with a field matching
892 the expression are shown:
</para>
894 <programlisting>journalctl _SYSTEMD_UNIT=avahi-daemon.service
</programlisting>
896 <para>If two different fields are matched, only entries matching
897 both expressions at the same time are shown:
</para>
899 <programlisting>journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=
28097</programlisting>
901 <para>If two matches refer to the same field, all entries matching
902 either expression are shown:
</para>
904 <programlisting>journalctl _SYSTEMD_UNIT=avahi-daemon.service _SYSTEMD_UNIT=dbus.service
</programlisting>
906 <para>If the separator
<literal>+
</literal> is used, two
907 expressions may be combined in a logical OR. The following will
908 show all messages from the Avahi service process with the PID
909 28097 plus all messages from the D-Bus service (from any of its
912 <programlisting>journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=
28097 + _SYSTEMD_UNIT=dbus.service
</programlisting>
914 <para>Show all logs generated by the D-Bus executable:
</para>
916 <programlisting>journalctl /usr/bin/dbus-daemon
</programlisting>
918 <para>Show all kernel logs from previous boot:
</para>
920 <programlisting>journalctl -k -b -
1</programlisting>
922 <para>Show a live log display from a system service
923 <filename>apache.service
</filename>:
</para>
925 <programlisting>journalctl -f -u apache
</programlisting>
930 <title>See Also
</title>
932 <citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
933 <citerefentry><refentrytitle>systemd-journald.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
934 <citerefentry><refentrytitle>systemctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
935 <citerefentry><refentrytitle>coredumpctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
936 <citerefentry><refentrytitle>systemd.journal-fields
</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
937 <citerefentry><refentrytitle>journald.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
938 <citerefentry><refentrytitle>systemd.time
</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
939 <citerefentry><refentrytitle>systemd-journal-remote
</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
940 <citerefentry><refentrytitle>systemd-journal-upload
</refentrytitle><manvolnum>8</manvolnum></citerefentry>