2012-03-16 00:50:52 +01: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 00:20:58 +02: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 00:50:52 +01: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 00:20:58 +02:00
|
|
|
Lesser General Public License for more details.
|
2012-03-16 00:50:52 +01:00
|
|
|
|
2012-04-12 00:20:58 +02:00
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
2012-03-16 00:50:52 +01:00
|
|
|
along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
-->
|
|
|
|
|
|
2014-02-12 06:55:38 +01:00
|
|
|
<refentry id="journalctl"
|
|
|
|
|
xmlns:xi="http://www.w3.org/2001/XInclude">
|
2012-03-16 00:50:52 +01:00
|
|
|
|
|
|
|
|
<refentryinfo>
|
2012-03-26 20:58:47 +02:00
|
|
|
<title>journalctl</title>
|
2012-03-16 00:50:52 +01: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 20:58:47 +02:00
|
|
|
<refentrytitle>journalctl</refentrytitle>
|
2012-03-16 00:50:52 +01:00
|
|
|
<manvolnum>1</manvolnum>
|
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
|
|
<refnamediv>
|
2012-03-26 20:58:47 +02:00
|
|
|
<refname>journalctl</refname>
|
2012-03-16 00:50:52 +01:00
|
|
|
<refpurpose>Query the systemd journal</refpurpose>
|
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
|
<cmdsynopsis>
|
2013-03-20 01:54:04 +01:00
|
|
|
<command>journalctl</command>
|
|
|
|
|
<arg choice="opt" rep="repeat">OPTIONS</arg>
|
|
|
|
|
<arg choice="opt" rep="repeat">MATCHES</arg>
|
2012-03-16 00:50:52 +01:00
|
|
|
</cmdsynopsis>
|
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
2012-06-01 01:05:38 +02:00
|
|
|
<para><command>journalctl</command> may be used to
|
|
|
|
|
query the contents of the
|
2012-03-16 00:50:52 +01:00
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
2012-06-01 01:05:38 +02:00
|
|
|
journal as written by
|
|
|
|
|
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
2012-03-16 00:50:52 +01:00
|
|
|
|
2013-07-02 05:44:04 +02:00
|
|
|
<para>If called without parameters, it will show the full
|
2012-03-16 00:50:52 +01:00
|
|
|
contents of the journal, starting with the oldest
|
|
|
|
|
entry collected.</para>
|
|
|
|
|
|
2013-07-02 05:44:04 +02:00
|
|
|
<para>If one or more match arguments are passed, the
|
2012-07-13 00:29:26 +02:00
|
|
|
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-03 22:31:48 +02:00
|
|
|
<citerefentry><refentrytitle>systemd.journal-fields</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
2012-07-13 00:29:26 +02:00
|
|
|
for a list of well-known fields. If multiple matches
|
2013-07-02 05:44:04 +02:00
|
|
|
are specified matching different fields, the log
|
2012-07-13 00:29:26 +02:00
|
|
|
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
|
2014-07-20 03:05:07 +02:00
|
|
|
same field. Finally, the character
|
|
|
|
|
<literal>+</literal> may appears as a separate word
|
|
|
|
|
between other terms on the command line. This causes
|
|
|
|
|
all matches before and after to be combined in a
|
|
|
|
|
disjunction (i.e. logical OR).</para>
|
2012-03-16 00:50:52 +01:00
|
|
|
|
2012-08-09 17:05:29 +02:00
|
|
|
<para>As shortcuts for a few types of field/value
|
2013-07-02 05:44:04 +02:00
|
|
|
matches, file paths may be specified. If a file path
|
2012-08-09 17:05:29 +02:00
|
|
|
refers to an executable file, this is equivalent to an
|
|
|
|
|
<literal>_EXE=</literal> match for the canonicalized
|
2013-07-02 05:44:04 +02:00
|
|
|
binary path. Similarly, if a path refers to a device
|
2012-08-09 17:05:29 +02:00
|
|
|
node, this is equivalent to a
|
|
|
|
|
<literal>_KERNEL_DEVICE=</literal> match for the
|
|
|
|
|
device.</para>
|
|
|
|
|
|
2014-08-19 23:21:43 +02:00
|
|
|
<para>Additional constraints may be added using options
|
2014-07-20 03:05:07 +02:00
|
|
|
<option>--boot</option>, <option>--unit=</option>,
|
2014-08-19 23:21:43 +02:00
|
|
|
etc, to further limit what entries will be shown
|
2014-07-20 03:05:07 +02:00
|
|
|
(logical AND).</para>
|
|
|
|
|
|
2012-03-16 00:50:52 +01:00
|
|
|
<para>Output is interleaved from all accessible
|
|
|
|
|
journal files, whether they are rotated or currently
|
2013-07-02 05:44:04 +02:00
|
|
|
being written, and regardless of whether they belong to the
|
2012-03-16 00:50:52 +01:00
|
|
|
system itself or are accessible user journals.</para>
|
|
|
|
|
|
2014-07-20 03:05:07 +02:00
|
|
|
<para>The set of journal files which will be used
|
|
|
|
|
can be modified using the <option>--user</option>,
|
|
|
|
|
<option>--system</option>, <option>--directory</option>,
|
|
|
|
|
and <option>--file</option> options, see below.</para>
|
|
|
|
|
|
2012-03-16 00:50:52 +01:00
|
|
|
<para>All users are granted access to their private
|
2013-07-02 05:44:04 +02:00
|
|
|
per-user journals. However, by default, only root and
|
2013-09-24 20:39:40 +02:00
|
|
|
users who are members of the <literal>systemd-journal</literal>
|
2012-03-16 00:50:52 +01:00
|
|
|
group get access to the system journal and the
|
|
|
|
|
journals of other users.</para>
|
2013-07-16 03:03:17 +02:00
|
|
|
|
|
|
|
|
<para>The output is paged through
|
|
|
|
|
<command>less</command> by default, and long lines are
|
|
|
|
|
"truncated" to screen width. The hidden part can be
|
|
|
|
|
viewed by using the left-arrow and right-arrow
|
2013-12-18 00:48:42 +01:00
|
|
|
keys. Paging can be disabled; see the
|
|
|
|
|
<option>--no-pager</option> option and the "Environment"
|
|
|
|
|
section below.</para>
|
2013-07-16 03:03:17 +02:00
|
|
|
|
2014-08-19 23:21:43 +02:00
|
|
|
<para>When outputting to a tty, lines are colored
|
2013-07-16 03:03:17 +02:00
|
|
|
according to priority: lines of level ERROR and higher
|
2013-12-18 00:48:42 +01:00
|
|
|
are colored red; lines of level NOTICE and higher are
|
2013-12-26 02:47:45 +01:00
|
|
|
highlighted; other lines are displayed normally.
|
2013-07-16 03:03:17 +02:00
|
|
|
</para>
|
2012-03-16 00:50:52 +01:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Options</title>
|
|
|
|
|
|
|
|
|
|
<para>The following options are understood:</para>
|
|
|
|
|
|
|
|
|
|
<variablelist>
|
2012-11-17 15:27:59 +01:00
|
|
|
<varlistentry>
|
2013-10-07 03:55:18 +02:00
|
|
|
<term><option>--no-full</option></term>
|
2012-11-17 15:27:59 +01:00
|
|
|
<term><option>--full</option></term>
|
2013-10-07 03:55:18 +02:00
|
|
|
<term><option>-l</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Ellipsize fields when
|
2013-10-15 08:58:51 +02:00
|
|
|
they do not fit in available columns.
|
2013-10-07 03:55:18 +02:00
|
|
|
The default is to show full fields,
|
|
|
|
|
allowing them to wrap or be truncated
|
2013-12-18 00:48:42 +01:00
|
|
|
by the pager, if one is used.</para>
|
2012-11-17 15:27:59 +01:00
|
|
|
|
2013-10-15 08:58:51 +02:00
|
|
|
<para>The old options
|
2013-10-07 03:55:18 +02:00
|
|
|
<option>-l</option>/<option>--full</option>
|
2013-10-15 08:58:51 +02:00
|
|
|
are not useful anymore, except to undo
|
2013-10-07 03:55:18 +02:00
|
|
|
<option>--no-full</option>.</para></listitem>
|
2012-11-17 15:27:59 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-03-16 00:50:52 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-a</option></term>
|
2013-02-13 10:39:22 +01:00
|
|
|
<term><option>--all</option></term>
|
2012-03-16 00:50:52 +01: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 10:39:22 +01:00
|
|
|
<term><option>--follow</option></term>
|
2012-03-16 00:50:52 +01:00
|
|
|
|
2012-09-05 23:08:06 +02:00
|
|
|
<listitem><para>Show only the most recent
|
2012-07-15 10:41:40 +02:00
|
|
|
journal entries, and continuously print
|
2012-03-16 01:00:23 +01:00
|
|
|
new entries as they are appended to
|
|
|
|
|
the journal.</para></listitem>
|
2012-03-16 00:50:52 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-03-07 20:44:35 +01: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-07 21:49:12 +01:00
|
|
|
implied pager tool. This implies
|
|
|
|
|
<option>-n1000</option> to guarantee
|
2013-07-02 05:44:04 +02:00
|
|
|
that the pager will not buffer logs of
|
2013-03-13 23:09:49 +01:00
|
|
|
unbounded size. This may be overridden
|
2013-03-07 21:49:12 +01:00
|
|
|
with an explicit <option>-n</option>
|
2014-08-31 11:12:22 +02:00
|
|
|
with some other numeric value while
|
|
|
|
|
<option>-nall</option> will disable this cap.
|
|
|
|
|
Note that this option is only supported for the
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 00:25:54 +02:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>less</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
2013-03-07 20:44:35 +01:00
|
|
|
pager.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-03-16 00:50:52 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-n</option></term>
|
2013-02-13 10:39:22 +01:00
|
|
|
<term><option>--lines=</option></term>
|
2012-03-16 00:50:52 +01:00
|
|
|
|
2012-10-23 11:10:51 +02:00
|
|
|
<listitem><para>Show the most recent
|
|
|
|
|
journal events and limit the number of
|
|
|
|
|
events shown. If
|
|
|
|
|
<option>--follow</option> is used,
|
2014-08-31 11:12:22 +02:00
|
|
|
this option is implied. The argument is
|
|
|
|
|
a positive integer or <literal>all</literal>
|
|
|
|
|
to disable line limiting. The default value is
|
|
|
|
|
10 if no argument is given.</para></listitem>
|
2012-03-16 00:50:52 +01: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 10:27:10 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-r</option></term>
|
|
|
|
|
<term><option>--reverse</option></term>
|
|
|
|
|
|
2013-12-26 02:47:45 +01:00
|
|
|
<listitem><para>Reverse output so that the newest
|
2013-03-01 10:27:10 +01:00
|
|
|
entries are displayed first.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-03-16 00:50:52 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-o</option></term>
|
2013-02-13 10:39:22 +01:00
|
|
|
<term><option>--output=</option></term>
|
2012-03-16 00:50:52 +01:00
|
|
|
|
|
|
|
|
<listitem><para>Controls the
|
2012-07-19 23:39:53 +02:00
|
|
|
formatting of the journal entries that
|
2013-07-16 10:20:03 +02:00
|
|
|
are shown. Takes one of the following options:
|
|
|
|
|
</para>
|
|
|
|
|
<variablelist>
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
|
|
|
|
<option>short</option>
|
|
|
|
|
</term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>is the default
|
|
|
|
|
and generates an output
|
|
|
|
|
that is mostly identical
|
|
|
|
|
to the formatting of
|
|
|
|
|
classic syslog files,
|
|
|
|
|
showing one line per
|
|
|
|
|
journal entry.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
2013-08-04 15:04:20 +02:00
|
|
|
<option>short-iso</option>
|
2013-07-16 10:20:03 +02:00
|
|
|
</term>
|
|
|
|
|
<listitem>
|
2013-08-04 15:04:20 +02:00
|
|
|
<para>is very similar,
|
|
|
|
|
but shows ISO 8601
|
2013-07-16 10:20:03 +02:00
|
|
|
wallclock timestamps.
|
|
|
|
|
</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
2013-08-04 15:04:20 +02:00
|
|
|
<option>short-precise</option>
|
2013-07-18 10:21:45 +02:00
|
|
|
</term>
|
|
|
|
|
<listitem>
|
2013-07-21 06:53:14 +02:00
|
|
|
<para>is very similar,
|
2013-08-04 15:04:20 +02:00
|
|
|
but shows timestamps
|
|
|
|
|
with full microsecond
|
|
|
|
|
precision.
|
|
|
|
|
</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
|
|
|
|
<option>short-monotonic</option>
|
|
|
|
|
</term>
|
|
|
|
|
<listitem>
|
2013-08-25 09:01:45 +02:00
|
|
|
<para>is very similar,
|
2013-08-04 15:04:20 +02:00
|
|
|
but shows monotonic
|
|
|
|
|
timestamps instead of
|
2013-07-18 10:21:45 +02:00
|
|
|
wallclock timestamps.
|
|
|
|
|
</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
2013-07-16 10:20:03 +02:00
|
|
|
<option>verbose</option>
|
|
|
|
|
</term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>shows the
|
|
|
|
|
full-structured entry
|
|
|
|
|
items with all fields.
|
|
|
|
|
</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
|
|
|
|
<option>export</option>
|
|
|
|
|
</term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>serializes the
|
|
|
|
|
journal into a binary
|
|
|
|
|
(but mostly text-based)
|
|
|
|
|
stream suitable for
|
|
|
|
|
backups and network
|
|
|
|
|
transfer (see <ulink
|
|
|
|
|
url="http://www.freedesktop.org/wiki/Software/systemd/export">Journal
|
|
|
|
|
Export Format</ulink>
|
|
|
|
|
for more
|
|
|
|
|
information).</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
|
|
|
|
<option>json</option>
|
|
|
|
|
</term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>formats entries
|
|
|
|
|
as JSON data structures,
|
|
|
|
|
one per line (see <ulink
|
|
|
|
|
url="http://www.freedesktop.org/wiki/Software/systemd/json">Journal
|
|
|
|
|
JSON Format</ulink> for
|
|
|
|
|
more information).</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
|
|
|
|
<option>json-pretty</option>
|
|
|
|
|
</term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>formats entries as
|
|
|
|
|
JSON data structures,
|
|
|
|
|
but formats them in
|
|
|
|
|
multiple lines in order
|
|
|
|
|
to make them more
|
2013-12-18 00:48:42 +01:00
|
|
|
readable by humans.</para>
|
2013-07-16 10:20:03 +02:00
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
|
|
|
|
<option>json-sse</option>
|
|
|
|
|
</term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>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>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term>
|
|
|
|
|
<option>cat</option>
|
|
|
|
|
</term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>generates a very
|
2013-12-18 00:48:42 +01:00
|
|
|
terse output, only
|
2013-07-16 10:20:03 +02:00
|
|
|
showing the actual
|
|
|
|
|
message of each journal
|
2014-02-17 03:37:18 +01:00
|
|
|
entry with no metadata,
|
2013-07-16 10:20:03 +02:00
|
|
|
not even a timestamp.
|
|
|
|
|
</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
</variablelist>
|
|
|
|
|
</listitem>
|
2012-03-16 00:50:52 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2014-10-02 14:39:29 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--utc</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Express time in Coordinated Universal
|
|
|
|
|
Time (UTC).</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-11-15 23:03:31 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-x</option></term>
|
2013-02-13 10:39:22 +01:00
|
|
|
<term><option>--catalog</option></term>
|
2012-11-15 23:03:31 +01: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
|
2013-09-10 14:27:15 +02:00
|
|
|
documentation, and any other relevant
|
2012-11-15 23:03:31 +01:00
|
|
|
manuals. Note that help texts are not
|
2012-11-16 03:04:08 +01:00
|
|
|
available for all messages, but only
|
|
|
|
|
for selected ones. For more
|
2013-07-02 05:44:04 +02:00
|
|
|
information on the message catalog,
|
2012-11-16 03:04:08 +01:00
|
|
|
please refer to the <ulink
|
|
|
|
|
url="http://www.freedesktop.org/wiki/Software/systemd/catalog">Message
|
|
|
|
|
Catalog Developer
|
2013-09-10 14:27:15 +02:00
|
|
|
Documentation</ulink>.</para>
|
|
|
|
|
|
|
|
|
|
<para>Note: when attaching
|
|
|
|
|
<command>journalctl</command> output
|
|
|
|
|
to bug reports, please do
|
|
|
|
|
<emphasis>not</emphasis> use
|
|
|
|
|
<option>-x</option>.</para>
|
|
|
|
|
</listitem>
|
2012-11-15 23:03:31 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-03-16 00:50:52 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-q</option></term>
|
2013-02-13 10:39:22 +01:00
|
|
|
<term><option>--quiet</option></term>
|
2012-03-16 00:50:52 +01:00
|
|
|
|
|
|
|
|
<listitem><para>Suppresses any warning
|
2013-12-18 00:48:42 +01:00
|
|
|
messages regarding inaccessible system
|
|
|
|
|
journals when run as a normal
|
2012-03-16 00:50:52 +01:00
|
|
|
user.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-03-27 00:14:29 +02:00
|
|
|
<varlistentry>
|
2012-09-06 01:49:00 +02:00
|
|
|
<term><option>-m</option></term>
|
2013-02-13 10:39:22 +01:00
|
|
|
<term><option>--merge</option></term>
|
2012-03-27 00:14:29 +02:00
|
|
|
|
2012-09-06 01:49:00 +02:00
|
|
|
<listitem><para>Show entries
|
|
|
|
|
interleaved from all available
|
|
|
|
|
journals, including remote
|
|
|
|
|
ones.</para></listitem>
|
2012-03-27 00:14:29 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-07-01 18:47:40 +02:00
|
|
|
<varlistentry>
|
2013-07-16 21:56:22 +02:00
|
|
|
<term><option>-b <optional><replaceable>ID</replaceable></optional><optional><replaceable>±offset</replaceable></optional></option></term>
|
|
|
|
|
<term><option>--boot=<optional><replaceable>ID</replaceable></optional><optional><replaceable>±offset</replaceable></optional></option></term>
|
2013-06-28 17:26:30 +02:00
|
|
|
|
2013-07-16 21:56:22 +02:00
|
|
|
<listitem><para>Show messages from a specific
|
|
|
|
|
boot. This will add a match for
|
2013-06-28 17:26:30 +02:00
|
|
|
<literal>_BOOT_ID=</literal>.</para>
|
|
|
|
|
|
2013-07-16 21:56:22 +02:00
|
|
|
<para>The argument may be empty, in which case
|
|
|
|
|
logs for the current boot will be shown.</para>
|
|
|
|
|
|
|
|
|
|
<para>If the boot ID is omitted, a positive
|
|
|
|
|
<replaceable>offset</replaceable> will look up
|
|
|
|
|
the boots starting from the beginning of the
|
|
|
|
|
journal, and a equal-or-less-than zero
|
|
|
|
|
<replaceable>offset</replaceable> will look up
|
|
|
|
|
boots starting from the end of the
|
|
|
|
|
journal. Thus, <constant>1</constant> means the
|
2013-12-18 00:48:42 +01:00
|
|
|
first boot found in the journal in
|
2013-07-16 21:56:22 +02:00
|
|
|
chronological order, <constant>2</constant> the
|
|
|
|
|
second and so on; while <constant>-0</constant>
|
|
|
|
|
is the last boot, <constant>-1</constant> the
|
2013-12-18 00:48:42 +01:00
|
|
|
boot before last, and so on. An empty
|
2013-07-16 21:56:22 +02:00
|
|
|
<replaceable>offset</replaceable> is equivalent
|
|
|
|
|
to specifying <constant>-0</constant>, except
|
|
|
|
|
when the current boot is not the last boot
|
|
|
|
|
(e.g. because <option>--directory</option> was
|
|
|
|
|
specified to look at logs from a different
|
|
|
|
|
machine).</para>
|
|
|
|
|
|
2013-12-18 00:48:42 +01:00
|
|
|
<para>If the 32-character
|
2013-07-16 21:56:22 +02:00
|
|
|
<replaceable>ID</replaceable> is specified, it
|
|
|
|
|
may optionally be followed by
|
|
|
|
|
<replaceable>offset</replaceable> which
|
|
|
|
|
identifies the boot relative to the one given by
|
|
|
|
|
boot <replaceable>ID</replaceable>. Negative
|
|
|
|
|
values mean earlier boots and a positive values
|
|
|
|
|
mean later boots. If
|
|
|
|
|
<replaceable>offset</replaceable> is not
|
2013-12-18 00:48:42 +01:00
|
|
|
specified, a value of zero is assumed, and the
|
2013-07-16 21:56:22 +02:00
|
|
|
logs for the boot given by
|
|
|
|
|
<replaceable>ID</replaceable> are shown.
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
</listitem>
|
2012-10-16 02:59:27 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-10-29 04:43:57 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--list-boots</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Show a tabular list of
|
2013-12-18 00:48:42 +01:00
|
|
|
boot numbers (relative to the current
|
2013-10-29 04:43:57 +01:00
|
|
|
boot), their IDs, and the timestamps
|
|
|
|
|
of the first and last message
|
|
|
|
|
pertaining to the boot.
|
|
|
|
|
</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-05-17 15:38:13 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-k</option></term>
|
|
|
|
|
<term><option>--dmesg</option></term>
|
|
|
|
|
|
2013-06-28 17:26:30 +02:00
|
|
|
<listitem><para>Show only kernel messages. This
|
|
|
|
|
implies <option>-b</option> and adds the match
|
|
|
|
|
<literal>_TRANSPORT=kernel</literal>.
|
2013-05-17 15:38:13 +02:00
|
|
|
</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2014-08-19 11:27:34 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-t</option></term>
|
|
|
|
|
<term><option>--identifier=<replaceable>SYSLOG_IDENTIFIER</replaceable>|<replaceable>PATTERN</replaceable></option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Show messages for the
|
|
|
|
|
specified syslog identifier
|
|
|
|
|
<replaceable>SYSLOG_IDENTIFIER</replaceable>, or
|
|
|
|
|
for any of the messages with a <literal>SYSLOG_IDENTIFIER</literal>
|
|
|
|
|
matched by <replaceable>PATTERN</replaceable>.</para>
|
|
|
|
|
|
|
|
|
|
<para>This parameter can be specified
|
|
|
|
|
multiple times.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-10-16 02:59:27 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-u</option></term>
|
2013-12-29 01:47:36 +01:00
|
|
|
<term><option>--unit=<replaceable>UNIT</replaceable>|<replaceable>PATTERN</replaceable></option></term>
|
2012-10-16 02:59:27 +02:00
|
|
|
|
2013-03-14 00:30:05 +01:00
|
|
|
<listitem><para>Show messages for the
|
2013-12-29 01:47:36 +01:00
|
|
|
specified systemd unit
|
2014-08-18 19:08:03 +02:00
|
|
|
<replaceable>UNIT</replaceable> (such
|
|
|
|
|
as a service unit), or for any of the
|
|
|
|
|
units matched by
|
2013-12-29 01:47:36 +01:00
|
|
|
<replaceable>PATTERN</replaceable>.
|
|
|
|
|
If a pattern is specified, a list of
|
|
|
|
|
unit names found in the journal is
|
|
|
|
|
compared with the specified pattern
|
|
|
|
|
and all that match are used. For each
|
2014-02-17 03:37:13 +01:00
|
|
|
unit name, a match is added for
|
2013-12-29 01:47:36 +01:00
|
|
|
messages from the unit
|
2014-02-17 03:37:13 +01:00
|
|
|
(<literal>_SYSTEMD_UNIT=<replaceable>UNIT</replaceable></literal>),
|
2013-12-29 01:47:36 +01:00
|
|
|
along with additional matches for
|
|
|
|
|
messages from systemd and messages
|
|
|
|
|
about coredumps for the specified
|
|
|
|
|
unit.</para>
|
|
|
|
|
|
|
|
|
|
<para>This parameter can be specified
|
2014-02-17 03:37:13 +01:00
|
|
|
multiple times.</para></listitem>
|
2013-03-01 14:39:04 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--user-unit=</option></term>
|
|
|
|
|
|
2013-03-14 00:30:05 +01:00
|
|
|
<listitem><para>Show messages for the
|
2013-03-01 14:39:04 +01:00
|
|
|
specified user session unit. This will
|
2013-03-14 00:30:05 +01: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
|
2013-04-12 09:14:43 +02:00
|
|
|
coredumps for the specified unit.</para>
|
|
|
|
|
<para>This parameter can be specified multiple times.
|
2013-03-14 00:30:05 +01:00
|
|
|
</para></listitem>
|
2012-10-16 02:59:27 +02: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
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 00:25:54 +02:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2012-10-16 02:59:27 +02:00
|
|
|
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
|
2013-07-02 05:44:04 +02:00
|
|
|
single log level is specified, all
|
2012-10-16 02:59:27 +02:00
|
|
|
messages with this log level or a
|
|
|
|
|
lower (hence more important) log level
|
2013-07-02 05:44:04 +02:00
|
|
|
are shown. If a range is specified, all
|
2012-10-16 02:59:27 +02:00
|
|
|
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 18:47:40 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-09-27 23:25:23 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-c</option></term>
|
2013-02-13 10:39:22 +01:00
|
|
|
<term><option>--cursor=</option></term>
|
2012-09-27 23:25:23 +02:00
|
|
|
|
2012-10-11 16:42:46 +02:00
|
|
|
<listitem><para>Start showing entries
|
|
|
|
|
from the location in the journal
|
|
|
|
|
specified by the passed
|
2012-09-27 23:25:23 +02:00
|
|
|
cursor.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-07-16 16:21:18 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--after-cursor=</option></term>
|
|
|
|
|
|
2013-12-17 05:40:00 +01:00
|
|
|
<listitem><para>Start showing entries
|
|
|
|
|
from the location in the journal
|
|
|
|
|
<emphasis>after</emphasis> the
|
|
|
|
|
location specified by the this cursor.
|
|
|
|
|
The cursor is shown when the
|
|
|
|
|
<option>--show-cursor</option> option
|
|
|
|
|
is used.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--show-cursor</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>The cursor is shown after the last
|
|
|
|
|
entry after two dashes:</para>
|
|
|
|
|
<programlisting>-- cursor: s=0639...</programlisting>
|
2013-12-18 00:48:42 +01:00
|
|
|
<para>The format of the cursor is private
|
|
|
|
|
and subject to change.</para></listitem>
|
2013-07-16 16:21:18 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-10-11 16:42:46 +02: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 20:59:12 +02:00
|
|
|
on or newer than the specified date,
|
|
|
|
|
or on or older than the specified
|
2013-06-26 14:03:53 +02:00
|
|
|
date, respectively. Date specifications
|
|
|
|
|
should be of the format
|
|
|
|
|
<literal>2012-10-30 18:17:16</literal>.
|
|
|
|
|
If the time part is omitted,
|
|
|
|
|
<literal>00:00:00</literal> is assumed.
|
|
|
|
|
If only the seconds component is omitted,
|
|
|
|
|
<literal>:00</literal> is assumed. If the
|
|
|
|
|
date component is omitted, the current
|
|
|
|
|
day is assumed. Alternatively the strings
|
2012-10-11 16:42:46 +02:00
|
|
|
<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 20:59:12 +02:00
|
|
|
current day, or the day after the
|
|
|
|
|
current day, respectively. <literal>now</literal>
|
2012-10-11 16:42:46 +02: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 20:59:12 +02:00
|
|
|
times before or after the current
|
|
|
|
|
time, respectively.</para></listitem>
|
2012-10-11 16:42:46 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-10-18 03:33:44 +02:00
|
|
|
<varlistentry>
|
2012-10-18 22:56:03 +02:00
|
|
|
<term><option>-F</option></term>
|
2013-02-13 10:39:22 +01:00
|
|
|
<term><option>--field=</option></term>
|
2012-10-18 03:33:44 +02:00
|
|
|
|
|
|
|
|
<listitem><para>Print all possible
|
|
|
|
|
data values the specified field can
|
|
|
|
|
take in all entries of the
|
|
|
|
|
journal.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-06-05 01:33:34 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--system</option></term>
|
|
|
|
|
<term><option>--user</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Show messages from
|
|
|
|
|
system services and the kernel (with
|
2013-12-18 00:48:42 +01:00
|
|
|
<option>--system</option>). Show
|
2013-06-05 01:33:34 +02:00
|
|
|
messages from service of current user
|
|
|
|
|
(with <option>--user</option>).
|
|
|
|
|
If neither is specified, show all
|
|
|
|
|
messages that the user can see.
|
|
|
|
|
</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-12-11 22:04:03 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>-M</option></term>
|
|
|
|
|
<term><option>--machine=</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Show messages from a
|
|
|
|
|
running, local container. Specify a
|
|
|
|
|
container name to connect
|
|
|
|
|
to.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-07-11 01:08:38 +02:00
|
|
|
<varlistentry>
|
2013-06-06 01:30:17 +02:00
|
|
|
<term><option>-D <replaceable>DIR</replaceable></option></term>
|
|
|
|
|
<term><option>--directory=<replaceable>DIR</replaceable></option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a directory path
|
2013-07-02 05:44:04 +02:00
|
|
|
as argument. If specified, journalctl
|
2013-06-06 01:30:17 +02:00
|
|
|
will operate on the specified journal
|
|
|
|
|
directory
|
|
|
|
|
<replaceable>DIR</replaceable> instead
|
|
|
|
|
of the default runtime and system
|
|
|
|
|
journal paths.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--file=<replaceable>GLOB</replaceable></option></term>
|
|
|
|
|
|
2013-12-18 00:48:42 +01:00
|
|
|
<listitem><para>Takes a file glob as an
|
2013-07-02 05:44:04 +02:00
|
|
|
argument. If specified, journalctl will
|
2013-06-06 01:30:17 +02:00
|
|
|
operate on the specified journal files
|
|
|
|
|
matching <replaceable>GLOB</replaceable>
|
|
|
|
|
instead of the default runtime and
|
|
|
|
|
system journal paths. May be specified
|
2013-12-26 02:47:44 +01:00
|
|
|
multiple times, in which case files will
|
2013-06-06 01:30:17 +02:00
|
|
|
be suitably interleaved.</para></listitem>
|
2012-07-11 01:08:38 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-03-29 02:44:00 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--root=<replaceable>ROOT</replaceable></option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a directory path
|
2013-12-18 00:48:42 +01:00
|
|
|
as an argument. If specified, journalctl
|
2013-03-29 02:44:00 +01:00
|
|
|
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 01:09:43 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--new-id128</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Instead of showing
|
2013-12-18 00:48:42 +01:00
|
|
|
journal contents, generate a new 128-bit
|
|
|
|
|
ID suitable for identifying
|
2012-08-17 01:09:43 +02:00
|
|
|
messages. This is intended for usage
|
|
|
|
|
by developers who need a new
|
|
|
|
|
identifier for a new message they
|
|
|
|
|
introduce and want to make
|
2013-07-02 05:44:04 +02:00
|
|
|
recognizable. This will print the new ID in
|
2012-08-17 01:09:43 +02:00
|
|
|
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
|
2013-07-02 05:44:04 +02:00
|
|
|
journal contents, show internal header
|
2012-09-05 23:08:06 +02:00
|
|
|
information of the journal fields
|
2012-08-17 01:09:43 +02:00
|
|
|
accessed.</para></listitem>
|
2012-09-07 23:20:28 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--disk-usage</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Shows the current disk
|
2014-11-03 23:08:33 +01:00
|
|
|
usage of all journal files. This shows
|
|
|
|
|
the sum of the disk usage of all
|
|
|
|
|
archived and active journal
|
|
|
|
|
files.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--vacuum-size=</option></term>
|
|
|
|
|
<term><option>--vacuum-time=</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Removes archived
|
|
|
|
|
journal files until the disk space
|
|
|
|
|
they use falls below the specified
|
|
|
|
|
size (specified with the usual K, M,
|
|
|
|
|
G, T suffixes), or all journal files
|
|
|
|
|
contain no data older than the
|
|
|
|
|
specified timespan (specified with the
|
|
|
|
|
usual s, min, h, days, months, weeks,
|
|
|
|
|
years suffixes). Note that running
|
|
|
|
|
<option>--vacuum-size=</option> has
|
|
|
|
|
only indirect effect on the output
|
|
|
|
|
shown by <option>--disk-usage</option>
|
|
|
|
|
as the latter includes active journal
|
|
|
|
|
files, while the former only operates
|
|
|
|
|
on archived journal
|
|
|
|
|
files. <option>--vacuum-size=</option>
|
|
|
|
|
and <option>--vacuum-time=</option>
|
|
|
|
|
may be combined in a single invocation
|
|
|
|
|
to enforce both a size and time limit
|
|
|
|
|
on the archived journal
|
|
|
|
|
files.</para></listitem>
|
2012-11-15 23:03:31 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
2013-03-20 01:54:04 +01:00
|
|
|
<term><option>--list-catalog
|
2013-12-18 00:48:43 +01:00
|
|
|
<optional><replaceable>128-bit-ID...</replaceable></optional>
|
2013-03-20 01:54:04 +01:00
|
|
|
</option></term>
|
2012-11-15 23:03:31 +01:00
|
|
|
|
|
|
|
|
<listitem><para>List the contents of
|
2013-12-18 00:48:42 +01:00
|
|
|
the message catalog as a table of
|
|
|
|
|
message IDs, plus their short
|
2013-03-20 01:54:04 +01:00
|
|
|
description strings.</para>
|
|
|
|
|
|
|
|
|
|
<para>If any
|
2013-12-18 00:48:43 +01:00
|
|
|
<replaceable>128-bit-ID</replaceable>s are
|
2013-03-20 01:54:04 +01:00
|
|
|
specified, only those entries are shown.
|
|
|
|
|
</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--dump-catalog
|
2013-12-18 00:48:43 +01:00
|
|
|
<optional><replaceable>128-bit-ID...</replaceable></optional>
|
2013-03-20 01:54:04 +01:00
|
|
|
</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Show the contents of
|
|
|
|
|
the message catalog, with entries
|
|
|
|
|
separated by a line consisting of two
|
2013-12-18 00:48:42 +01:00
|
|
|
dashes and the ID (the format is the
|
2013-03-20 01:54:04 +01:00
|
|
|
same as <filename>.catalog</filename>
|
2013-12-18 00:48:42 +01:00
|
|
|
files).</para>
|
2013-03-20 01:54:04 +01:00
|
|
|
|
|
|
|
|
<para>If any
|
2013-12-18 00:48:43 +01:00
|
|
|
<replaceable>128-bit-ID</replaceable>s are
|
2013-03-20 01:54:04 +01:00
|
|
|
specified, only those entries are shown.
|
|
|
|
|
</para>
|
|
|
|
|
</listitem>
|
2012-11-15 23:03:31 +01: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
|
2013-12-18 00:48:42 +01:00
|
|
|
files are installed, removed, or
|
2012-11-15 23:03:31 +01:00
|
|
|
updated to rebuild the binary catalog
|
|
|
|
|
index.</para></listitem>
|
2012-08-17 01:09:43 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--setup-keys</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Instead of showing
|
2013-07-02 05:44:04 +02:00
|
|
|
journal contents, generate a new key
|
2012-08-17 01:09:43 +02:00
|
|
|
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
|
2013-12-18 01:40:02 +01:00
|
|
|
stored externally. Refer to the
|
2013-06-18 16:25:11 +02:00
|
|
|
<option>Seal=</option> option in
|
|
|
|
|
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
2013-12-18 01:40:02 +01:00
|
|
|
for information on Forward Secure
|
|
|
|
|
Sealing and for a link to a refereed
|
|
|
|
|
scholarly paper detailing the
|
|
|
|
|
cryptographic theory it is based on.
|
|
|
|
|
</para></listitem>
|
2012-08-17 01:09:43 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-07-15 05:13:09 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--force</option></term>
|
|
|
|
|
|
2013-12-18 00:48:42 +01:00
|
|
|
<listitem><para>When
|
|
|
|
|
<option>--setup-keys</option> is passed and
|
|
|
|
|
Forward Secure Sealing (FSS) has already been
|
|
|
|
|
configured, recreate FSS keys.</para></listitem>
|
2013-07-15 05:13:09 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-08-17 01:09:43 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--interval=</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Specifies the change
|
2013-07-02 05:44:04 +02:00
|
|
|
interval for the sealing key when
|
2012-08-17 01:09:43 +02:00
|
|
|
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
|
2013-07-02 05:44:04 +02:00
|
|
|
enabled and the FSS verification key
|
2012-08-17 01:09:43 +02:00
|
|
|
has been specified with
|
2013-07-02 05:44:04 +02:00
|
|
|
<option>--verify-key=</option>,
|
2012-08-17 01:09:43 +02:00
|
|
|
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>
|
|
|
|
|
|
2014-10-23 00:28:17 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><option>--flush</option></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Asks the Journal
|
|
|
|
|
daemon to flush any log data stored in
|
2014-10-29 11:20:02 +01:00
|
|
|
<filename>/run/log/journal</filename>
|
2014-10-23 00:28:17 +02:00
|
|
|
into
|
2014-10-29 11:20:02 +01:00
|
|
|
<filename>/var/log/journal</filename>,
|
2014-10-23 00:28:17 +02:00
|
|
|
if persistent storage is enabled. This
|
|
|
|
|
call does not return until the
|
|
|
|
|
operation is
|
|
|
|
|
complete.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2014-02-13 20:33:51 +01:00
|
|
|
<xi:include href="standard-options.xml" xpointer="help" />
|
|
|
|
|
<xi:include href="standard-options.xml" xpointer="version" />
|
|
|
|
|
<xi:include href="standard-options.xml" xpointer="no-pager" />
|
2012-03-16 00:50:52 +01:00
|
|
|
</variablelist>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Exit status</title>
|
|
|
|
|
|
2013-12-18 00:48:42 +01:00
|
|
|
<para>On success, 0 is returned; otherwise, a non-zero
|
|
|
|
|
failure code is returned.</para>
|
2012-03-16 00:50:52 +01:00
|
|
|
</refsect1>
|
|
|
|
|
|
2014-02-12 06:55:38 +01:00
|
|
|
<xi:include href="less-variables.xml" />
|
2012-03-16 00:50:52 +01:00
|
|
|
|
2012-07-13 00:29:26 +02:00
|
|
|
<refsect1>
|
|
|
|
|
<title>Examples</title>
|
|
|
|
|
|
2013-07-02 05:44:04 +02:00
|
|
|
<para>Without arguments, all collected logs are shown
|
2012-07-13 00:29:26 +02:00
|
|
|
unfiltered:</para>
|
|
|
|
|
|
|
|
|
|
<programlisting>journalctl</programlisting>
|
|
|
|
|
|
2013-07-02 05:44:04 +02:00
|
|
|
<para>With one match specified, all entries with a field matching the expression are shown:</para>
|
2012-07-13 00:29:26 +02:00
|
|
|
|
|
|
|
|
<programlisting>journalctl _SYSTEMD_UNIT=avahi-daemon.service</programlisting>
|
|
|
|
|
|
2013-07-02 05:44:04 +02:00
|
|
|
<para>If two different fields are matched, only entries matching both expressions at the same time are shown:</para>
|
2012-07-13 00:29:26 +02:00
|
|
|
|
|
|
|
|
<programlisting>journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097</programlisting>
|
|
|
|
|
|
2013-07-02 05:44:04 +02:00
|
|
|
<para>If two matches refer to the same field, all entries matching either expression are shown:</para>
|
2012-07-13 00:29:26 +02:00
|
|
|
|
|
|
|
|
<programlisting>journalctl _SYSTEMD_UNIT=avahi-daemon.service _SYSTEMD_UNIT=dbus.service</programlisting>
|
|
|
|
|
|
2013-07-02 05:44:04 +02:00
|
|
|
<para>If the separator <literal>+</literal> is used,
|
2012-09-05 23:08:06 +02:00
|
|
|
two expressions may be combined in a logical OR. The
|
2012-07-13 00:29:26 +02: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 17:05:29 +02:00
|
|
|
<para>Show all logs generated by the D-Bus executable:</para>
|
|
|
|
|
|
|
|
|
|
<programlisting>journalctl /usr/bin/dbus-daemon</programlisting>
|
|
|
|
|
|
2013-05-03 06:55:20 +02:00
|
|
|
<para>Show all logs of the kernel device node <filename noindex='true'>/dev/sda</filename>:</para>
|
2012-08-09 17:05:29 +02:00
|
|
|
|
|
|
|
|
<programlisting>journalctl /dev/sda</programlisting>
|
|
|
|
|
|
2013-07-19 13:54:51 +02:00
|
|
|
<para>Show all kernel logs from previous boot:</para>
|
2013-06-28 17:26:30 +02:00
|
|
|
|
2013-07-19 13:54:51 +02:00
|
|
|
<programlisting>journalctl -k -b -1</programlisting>
|
2013-06-28 17:26:30 +02:00
|
|
|
|
2014-08-18 19:08:03 +02:00
|
|
|
<para>Show a live log display from a system service <filename>apache.service</filename>:</para>
|
|
|
|
|
|
|
|
|
|
<programlisting>journalctl -f -u apache</programlisting>
|
|
|
|
|
|
2012-07-13 00:29:26 +02:00
|
|
|
</refsect1>
|
|
|
|
|
|
2012-03-16 00:50:52 +01:00
|
|
|
<refsect1>
|
|
|
|
|
<title>See Also</title>
|
|
|
|
|
<para>
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
2012-06-01 01:05:38 +02:00
|
|
|
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2012-03-16 00:50:52 +01:00
|
|
|
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
2014-07-14 02:32:46 +02:00
|
|
|
<citerefentry><refentrytitle>coredumpctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
2012-04-03 22:31:48 +02:00
|
|
|
<citerefentry><refentrytitle>systemd.journal-fields</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
2012-03-30 23:18:33 +02:00
|
|
|
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
2012-03-16 00:50:52 +01:00
|
|
|
</para>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
</refentry>
|