2012-03-16 03:50:52 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2012 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
2012-04-12 02:20:58 +04:00
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
2012-03-16 03:50:52 +04:00
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
2012-04-12 02:20:58 +04:00
Lesser General Public License for more details.
2012-03-16 03:50:52 +04:00
2012-04-12 02:20:58 +04:00
You should have received a copy of the GNU Lesser General Public License
2012-03-16 03:50:52 +04:00
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
2012-03-26 22:58:47 +04:00
<refentry id= "journalctl" >
2012-03-16 03:50:52 +04:00
<refentryinfo >
2012-03-26 22:58:47 +04:00
<title > journalctl</title>
2012-03-16 03:50:52 +04:00
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Lennart</firstname>
<surname > Poettering</surname>
<email > lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
2012-03-26 22:58:47 +04:00
<refentrytitle > journalctl</refentrytitle>
2012-03-16 03:50:52 +04:00
<manvolnum > 1</manvolnum>
</refmeta>
<refnamediv >
2012-03-26 22:58:47 +04:00
<refname > journalctl</refname>
2012-03-16 03:50:52 +04:00
<refpurpose > Query the systemd journal</refpurpose>
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
2013-03-20 04:54:04 +04:00
<command > journalctl</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "opt" rep= "repeat" > MATCHES</arg>
2012-03-16 03:50:52 +04:00
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2012-06-01 03:05:38 +04:00
<para > <command > journalctl</command> may be used to
query the contents of the
2012-03-16 03:50:52 +04:00
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2012-06-01 03:05:38 +04:00
journal as written by
<citerefentry > <refentrytitle > systemd-journald.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> .</para>
2012-03-16 03:50:52 +04:00
2012-09-06 01:08:06 +04:00
<para > If called without parameter it will show the full
2012-03-16 03:50:52 +04:00
contents of the journal, starting with the oldest
entry collected.</para>
2012-07-13 02:29:26 +04:00
<para > If one or more match arguments are passed the
output is filtered accordingly. A match is in the
format <literal > FIELD=VALUE</literal> ,
e.g. <literal > _SYSTEMD_UNIT=httpd.service</literal> ,
referring to the components of a structured journal
entry. See
2012-04-04 00:31:48 +04:00
<citerefentry > <refentrytitle > systemd.journal-fields</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
2012-07-13 02:29:26 +04:00
for a list of well-known fields. If multiple matches
are specified matching different fields the log
entries are filtered by both, i.e. the resulting output
will show only entries matching all the specified
matches of this kind. If two matches apply to the same
field, then they are automatically matched as
alternatives, i.e. the resulting output will show
entries matching any of the specified matches for the
same field. Finally, if the character
"<literal > +</literal> " appears as separate word on the
command line all matches before and after are combined
in a disjunction (i.e. logical OR).</para>
2012-03-16 03:50:52 +04:00
2012-08-09 19:05:29 +04:00
<para > As shortcuts for a few types of field/value
matches file paths may be specified. If a file path
refers to an executable file, this is equivalent to an
<literal > _EXE=</literal> match for the canonicalized
binary path. Similar, if a path refers to a device
node, this is equivalent to a
<literal > _KERNEL_DEVICE=</literal> match for the
device.</para>
2012-03-16 03:50:52 +04:00
<para > Output is interleaved from all accessible
journal files, whether they are rotated or currently
being written, and regardless whether they belong to the
system itself or are accessible user journals.</para>
<para > All users are granted access to their private
per-user journals. However, by default only root and
users who are members of the <literal > adm</literal>
group get access to the system journal and the
journals of other users.</para>
</refsect1>
<refsect1 >
<title > Options</title>
<para > The following options are understood:</para>
<variablelist >
<varlistentry >
<term > <option > -h</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --help</option> </term>
2012-03-16 03:50:52 +04:00
<listitem > <para > Prints a short help
text and exits.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --version</option> </term>
<listitem > <para > Prints a short version
string and exits.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --no-pager</option> </term>
2012-06-10 20:32:11 +04:00
<listitem > <para > Do not pipe output into a
pager.</para> </listitem>
</varlistentry>
2012-03-16 03:50:52 +04:00
2012-11-17 18:27:59 +04:00
<varlistentry >
<term > <option > --full</option> </term>
<listitem > <para > Show all (printable) fields in
full.</para> </listitem>
</varlistentry>
2012-03-16 03:50:52 +04:00
<varlistentry >
<term > <option > -a</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --all</option> </term>
2012-03-16 03:50:52 +04:00
<listitem > <para > Show all fields in
full, even if they include unprintable
characters or are very
long.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > -f</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --follow</option> </term>
2012-03-16 03:50:52 +04:00
2012-09-06 01:08:06 +04:00
<listitem > <para > Show only the most recent
2012-07-15 12:41:40 +04:00
journal entries, and continuously print
2012-03-16 04:00:23 +04:00
new entries as they are appended to
the journal.</para> </listitem>
2012-03-16 03:50:52 +04:00
</varlistentry>
2013-03-07 23:44:35 +04:00
<varlistentry >
<term > <option > -e</option> </term>
<term > <option > --pager-end</option> </term>
<listitem > <para > Immediately jump to
the end of the journal inside the
2013-03-08 00:49:12 +04:00
implied pager tool. This implies
<option > -n1000</option> to guarantee
that the pager won't buffer logs of
2013-03-14 02:09:49 +04:00
unbounded size. This may be overridden
2013-03-08 00:49:12 +04:00
with an explicit <option > -n</option>
with some other numeric value on the
command line. Note that this option is
only supported for the
2013-03-07 23:44:35 +04:00
<citerefentry > <refentrytitle > less</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
pager.</para> </listitem>
</varlistentry>
2012-03-16 03:50:52 +04:00
<varlistentry >
<term > <option > -n</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --lines=</option> </term>
2012-03-16 03:50:52 +04:00
2012-10-23 13:10:51 +04:00
<listitem > <para > Show the most recent
journal events and limit the number of
events shown. If
<option > --follow</option> is used,
this option is implied. The argument,
a positive integer, is optional, and
defaults to 10. </para> </listitem>
2012-03-16 03:50:52 +04:00
</varlistentry>
<varlistentry >
<term > <option > --no-tail</option> </term>
<listitem > <para > Show all stored output
lines, even in follow mode. Undoes the
effect of
<option > --lines=</option> .</para> </listitem>
</varlistentry>
2013-03-01 13:27:10 +04:00
<varlistentry >
<term > <option > -r</option> </term>
<term > <option > --reverse</option> </term>
<listitem > <para > Reverse output, so the newest
entries are displayed first.</para> </listitem>
</varlistentry>
2012-03-16 03:50:52 +04:00
<varlistentry >
<term > <option > -o</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --output=</option> </term>
2012-03-16 03:50:52 +04:00
<listitem > <para > Controls the
2012-07-20 01:39:53 +04:00
formatting of the journal entries that
are shown. Takes one of
2012-03-16 03:50:52 +04:00
<literal > short</literal> ,
<literal > short-monotonic</literal> ,
<literal > verbose</literal> ,
<literal > export</literal> ,
<literal > json</literal> ,
2012-09-06 02:25:32 +04:00
<literal > json-pretty</literal> ,
2012-10-11 04:37:10 +04:00
<literal > json-sse</literal> ,
2012-03-16 03:50:52 +04:00
<literal > cat</literal> . <literal > short</literal>
is the default and generates an output
that is mostly identical to the
formatting of classic syslog log
files, showing one line per journal
entry. <literal > short-monotonic</literal>
is very similar but shows monotonic
timestamps instead of wallclock
timestamps. <literal > verbose</literal>
2012-07-15 12:41:40 +04:00
shows the full structured entry items
2012-03-16 03:50:52 +04:00
with all
2012-07-15 12:41:40 +04:00
fields. <literal > export</literal>
2012-03-16 03:50:52 +04:00
serializes the journal into a binary
(but mostly text-based) stream
suitable for backups and network
2012-07-20 01:39:53 +04:00
transfer (see <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/export">Journal
Export Format</ulink> for more
information). <literal > json</literal>
2012-03-16 03:50:52 +04:00
formats entries as JSON data
2012-09-06 02:25:32 +04:00
structures, one per
2012-10-25 03:19:24 +04:00
line (see <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/json">Journal
JSON Format</ulink> for more
information). <literal > json-pretty</literal>
2012-09-06 02:25:32 +04:00
also formats entries as JSON data
structures, but formats them in
multiple lines in order to make them
more readable for
2012-10-11 04:37:10 +04:00
humans. <literal > json-sse</literal>
also formats entries as JSON data
structures, but wraps them in a format
suitable for <ulink
url="https://developer.mozilla.org/en-US/docs/Server-sent_events/Using_server-sent_events">Server-Sent
Events</ulink> . <literal > cat</literal>
2012-03-16 03:50:52 +04:00
generates a very terse output only
showing the actual message of each
journal entry with no meta data, not
even a timestamp.</para> </listitem>
</varlistentry>
2012-11-16 02:03:31 +04:00
<varlistentry >
<term > <option > -x</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --catalog</option> </term>
2012-11-16 02:03:31 +04:00
<listitem > <para > 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
2012-11-16 06:04:08 +04:00
available for all messages, but only
for selected ones. For more
information on the message catalog
please refer to the <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/catalog">Message
Catalog Developer
Documentation</ulink> .</para> </listitem>
2012-11-16 02:03:31 +04:00
</varlistentry>
2012-03-16 03:50:52 +04:00
<varlistentry >
<term > <option > -q</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --quiet</option> </term>
2012-03-16 03:50:52 +04:00
<listitem > <para > Suppresses any warning
2012-07-15 12:41:40 +04:00
message regarding inaccessible system
2012-03-16 03:50:52 +04:00
journals when run as normal
user.</para> </listitem>
</varlistentry>
2012-03-27 02:14:29 +04:00
<varlistentry >
2012-09-06 03:49:00 +04:00
<term > <option > -m</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --merge</option> </term>
2012-03-27 02:14:29 +04:00
2012-09-06 03:49:00 +04:00
<listitem > <para > Show entries
interleaved from all available
journals, including remote
ones.</para> </listitem>
2012-03-27 02:14:29 +04:00
</varlistentry>
2012-07-01 20:47:40 +04:00
<varlistentry >
<term > <option > -b</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --this-boot</option> </term>
2012-07-01 20:47:40 +04:00
<listitem > <para > Show data only from
2012-10-16 04:59:27 +04:00
current boot. This will add a match
for <literal > _BOOT_ID=</literal> for
the current boot ID of the
kernel.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > -u</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --unit=</option> </term>
2012-10-16 04:59:27 +04:00
2013-03-14 03:30:05 +04:00
<listitem > <para > Show messages for the
specified systemd unit. This will add
a match for messages from the unit
(<literal > _SYSTEMD_UNIT=</literal> )
and additional matches for messages
from systemd and messages about
coredumps for the specified unit.
</para> </listitem>
2013-03-01 17:39:04 +04:00
</varlistentry>
<varlistentry >
<term > <option > --user-unit=</option> </term>
2013-03-14 03:30:05 +04:00
<listitem > <para > Show messages for the
2013-03-01 17:39:04 +04:00
specified user session unit. This will
2013-03-14 03:30:05 +04:00
add a match for messages from the unit
(<literal > _SYSTEMD_USER_UNIT=</literal>
and <literal > _UID=</literal> ) and
additional matches for messages from
session systemd and messages about
coredumps for the specified unit.
</para> </listitem>
2012-10-16 04:59:27 +04:00
</varlistentry>
<varlistentry >
<term > <option > -p</option> </term>
<term > <option > --priority=</option> </term>
<listitem > <para > Filter output by
message priorities or priority
ranges. Takes either a single numeric
or textual log level (i.e. between
0/<literal > emerg</literal> and
7/<literal > debug</literal> ), 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
<citerefentry > <refentrytitle > syslog</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
i.e. <literal > emerg</literal> (0),
<literal > alert</literal> (1),
<literal > crit</literal> (2),
<literal > err</literal> (3),
<literal > warning</literal> (4),
<literal > notice</literal> (5),
<literal > info</literal> (6),
<literal > debug</literal> (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
<literal > PRIORITY=</literal> matches
for the specified
priorities.</para> </listitem>
2012-07-01 20:47:40 +04:00
</varlistentry>
2012-09-28 01:25:23 +04:00
<varlistentry >
<term > <option > -c</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --cursor=</option> </term>
2012-09-28 01:25:23 +04:00
2012-10-11 18:42:46 +04:00
<listitem > <para > Start showing entries
from the location in the journal
specified by the passed
2012-09-28 01:25:23 +04:00
cursor.</para> </listitem>
</varlistentry>
2012-10-11 18:42:46 +04:00
<varlistentry >
<term > <option > --since=</option> </term>
<term > <option > --until=</option> </term>
<listitem > <para > Start showing entries
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
on or newer than the specified date,
or on or older than the specified
date, respectively. Date specifications should be of
2012-10-11 18:42:46 +04:00
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
2012-11-29 23:06:57 +04:00
date component is omitted, the
2012-10-11 18:42:46 +04:00
current day is assumed. Alternatively
the strings
<literal > yesterday</literal> ,
<literal > today</literal> ,
<literal > tomorrow</literal> are
understood, which refer to 00:00:00 of
the day before the current day, the
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
current day, or the day after the
current day, respectively. <literal > now</literal>
2012-10-11 18:42:46 +04:00
refers to the current time. Finally,
relative times may be specified,
prefixed with <literal > -</literal> or
<literal > +</literal> , referring to
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
times before or after the current
time, respectively.</para> </listitem>
2012-10-11 18:42:46 +04:00
</varlistentry>
2012-10-18 05:33:44 +04:00
<varlistentry >
2012-10-19 00:56:03 +04:00
<term > <option > -F</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --field=</option> </term>
2012-10-18 05:33:44 +04:00
<listitem > <para > Print all possible
data values the specified field can
take in all entries of the
journal.</para> </listitem>
</varlistentry>
2012-07-11 03:08:38 +04:00
<varlistentry >
<term > <option > -D</option> </term>
2013-02-13 13:39:22 +04:00
<term > <option > --directory=</option> </term>
2012-07-11 03:08:38 +04:00
2012-11-04 19:19:04 +04:00
<listitem > <para > Takes a
2012-07-11 03:08:38 +04:00
directory path as argument. If
2012-09-06 01:08:06 +04:00
specified journalctl will operate on the
2012-07-11 03:08:38 +04:00
specified journal directory instead of
the default runtime and system journal
paths.</para> </listitem>
</varlistentry>
2013-03-29 05:44:00 +04:00
<varlistentry >
<term > <option > --root=<replaceable > ROOT</replaceable> </option> </term>
<listitem > <para > Takes a directory path
as argument. If specified journalctl
will operate on catalog file hierarchy
underneath the specified directory
instead of the root directory
(e.g. <option > --update-catalog</option>
will create
<filename > <replaceable > ROOT</replaceable> /var/lib/systemd/catalog/database</filename> ).
</para> </listitem>
</varlistentry>
2012-08-17 03:09:43 +04:00
<varlistentry >
<term > <option > --new-id128</option> </term>
<listitem > <para > Instead of showing
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
introduce and want to make
recognizable. Will print the new ID in
three different formats which can be
copied into source code or
similar.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --header</option> </term>
<listitem > <para > Instead of showing
journal contents show internal header
2012-09-06 01:08:06 +04:00
information of the journal fields
2012-08-17 03:09:43 +04:00
accessed.</para> </listitem>
2012-09-08 01:20:28 +04:00
</varlistentry>
<varlistentry >
<term > <option > --disk-usage</option> </term>
<listitem > <para > Shows the current disk
usage of all
journal files.</para> </listitem>
2012-11-16 02:03:31 +04:00
</varlistentry>
<varlistentry >
2013-03-20 04:54:04 +04:00
<term > <option > --list-catalog
<optional > <replaceable > ID128...</replaceable> </optional>
</option> </term>
2012-11-16 02:03:31 +04:00
<listitem > <para > List the contents of
the message catalog, as table of
message IDs plus their short
2013-03-20 04:54:04 +04:00
description strings.</para>
<para > If any
<replaceable > ID128</replaceable> s are
specified, only those entries are shown.
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <option > --dump-catalog
<optional > <replaceable > ID128...</replaceable> </optional>
</option> </term>
<listitem > <para > Show the contents of
the message catalog, with entries
separated by a line consisting of two
dashes and the id (the format is the
same as <filename > .catalog</filename>
files.</para>
<para > If any
<replaceable > ID128</replaceable> s are
specified, only those entries are shown.
</para>
</listitem>
2012-11-16 02:03:31 +04:00
</varlistentry>
<varlistentry >
<term > <option > --update-catalog</option> </term>
<listitem > <para > 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.</para> </listitem>
2012-08-17 03:09:43 +04:00
</varlistentry>
<varlistentry >
<term > <option > --setup-keys</option> </term>
<listitem > <para > 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.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --interval=</option> </term>
<listitem > <para > Specifies the change
interval for the sealing key, when
generating an FSS key pair with
<option > --setup-keys</option> . Shorter
intervals increase CPU consumption but
shorten the time range of
undetectable journal
alterations. Defaults to
15min.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --verify</option> </term>
<listitem > <para > 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
<option > --verify-key=</option>
authenticity of the journal file is
verified.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --verify-key=</option> </term>
<listitem > <para > Specifies the FSS
verification key to use for the
<option > --verify</option>
operation.</para> </listitem>
</varlistentry>
2012-03-16 03:50:52 +04:00
</variablelist>
</refsect1>
<refsect1 >
<title > Exit status</title>
<para > On success 0 is returned, a non-zero failure
code otherwise.</para>
</refsect1>
<refsect1 >
<title > Environment</title>
2013-01-26 19:47:16 +04:00
<variablelist class= 'environment-variables' >
2012-03-16 03:50:52 +04:00
<varlistentry >
<term > <varname > $SYSTEMD_PAGER</varname> </term>
<listitem > <para > Pager to use when
<option > --no-pager</option> is not given;
overrides <varname > $PAGER</varname> . Setting
this to an empty string or the value
<literal > cat</literal> is equivalent to passing
<option > --no-pager</option> .</para> </listitem>
</varlistentry>
</variablelist>
</refsect1>
2012-07-13 02:29:26 +04:00
<refsect1 >
<title > Examples</title>
<para > Without arguments all collected logs are shown
unfiltered:</para>
<programlisting > journalctl</programlisting>
<para > With one match specified all entries with a field matching the expression are shown:</para>
<programlisting > journalctl _SYSTEMD_UNIT=avahi-daemon.service</programlisting>
<para > If two different fields are matched only entries matching both expressions at the same time are shown:</para>
<programlisting > journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097</programlisting>
<para > If two matches refer to the same field all entries matching either expression are shown:</para>
<programlisting > journalctl _SYSTEMD_UNIT=avahi-daemon.service _SYSTEMD_UNIT=dbus.service</programlisting>
<para > If the separator "<literal > +</literal> " is used
2012-09-06 01:08:06 +04:00
two expressions may be combined in a logical OR. The
2012-07-13 02:29:26 +04:00
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
processes):</para>
<programlisting > journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097 + _SYSTEMD_UNIT=dbus.service</programlisting>
2012-08-09 19:05:29 +04:00
<para > Show all logs generated by the D-Bus executable:</para>
<programlisting > journalctl /usr/bin/dbus-daemon</programlisting>
<para > Show all logs of the kernel device node <filename > /dev/sda</filename> :</para>
<programlisting > journalctl /dev/sda</programlisting>
2012-07-13 02:29:26 +04:00
</refsect1>
2012-03-16 03:50:52 +04:00
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2012-06-01 03:05:38 +04:00
<citerefentry > <refentrytitle > systemd-journald.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
2012-03-16 03:50:52 +04:00
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2012-04-04 00:31:48 +04:00
<citerefentry > <refentrytitle > systemd.journal-fields</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ,
2012-03-31 01:18:33 +04:00
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2012-03-16 03:50:52 +04:00
</para>
</refsect1>
</refentry>
