2012-06-01 03:05:38 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
2023-12-25 17:48:33 +03:00
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2012-06-01 03:05:38 +04:00
2023-08-22 19:52:02 +03:00
<refentry id= "systemd-journald.service"
xmlns:xi="http://www.w3.org/2001/XInclude">
2012-06-01 03:05:38 +04:00
2015-02-04 05:14:13 +03:00
<refentryinfo >
<title > systemd-journald.service</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-journald.service</refentrytitle>
<manvolnum > 8</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-journald.service</refname>
<refname > systemd-journald.socket</refname>
<refname > systemd-journald-dev-log.socket</refname>
2015-10-12 06:25:43 +03:00
<refname > systemd-journald-audit.socket</refname>
2019-11-27 21:25:51 +03:00
<refname > systemd-journald@.service</refname>
<refname > systemd-journald@.socket</refname>
<refname > systemd-journald-varlink@.socket</refname>
2015-02-04 05:14:13 +03:00
<refname > systemd-journald</refname>
<refpurpose > Journal service</refpurpose>
</refnamediv>
<refsynopsisdiv >
2023-12-14 14:52:03 +03:00
<para > <simplelist >
<member > <filename > systemd-journald.service</filename> </member>
<member > <filename > systemd-journald.socket</filename> </member>
<member > <filename > systemd-journald-dev-log.socket</filename> </member>
<member > <filename > systemd-journald-audit.socket</filename> </member>
<member > <filename > systemd-journald@.service</filename> </member>
<member > <filename > systemd-journald@.socket</filename> </member>
<member > <filename > systemd-journald-varlink@.socket</filename> </member>
<member > <filename > /usr/lib/systemd/systemd-journald</filename> </member>
</simplelist> </para>
2015-02-04 05:14:13 +03:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <filename > systemd-journald</filename> is a system service
that collects and stores logging data. It creates and maintains
structured, indexed journals based on logging information that is
received from a variety of sources:</para>
<itemizedlist >
<listitem > <para > Kernel log messages, via kmsg</para> </listitem>
2017-09-15 15:17:32 +03:00
<listitem > <para > Simple system log messages, via the <filename > libc</filename> <citerefentry
project='man-pages'><refentrytitle > syslog</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
2015-02-04 05:14:13 +03:00
call</para> </listitem>
2021-04-08 23:14:57 +03:00
<listitem > <para > Structured system log messages via the native Journal API, see
<citerefentry > <refentrytitle > sd_journal_print</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
and <ulink url= "https://systemd.io/JOURNAL_NATIVE_PROTOCOL" > Native Journal
Protocol</ulink> </para> </listitem>
2015-02-04 05:14:13 +03:00
2017-09-15 15:17:32 +03:00
<listitem > <para > Standard output and standard error of service units. For further details see
below.</para> </listitem>
2015-02-04 05:14:13 +03:00
2017-09-15 15:17:32 +03:00
<listitem > <para > Audit records, originating from the kernel audit subsystem</para> </listitem>
2015-02-04 05:14:13 +03:00
</itemizedlist>
<para > The daemon will implicitly collect numerous metadata fields
for each log messages in a secure and unfakeable way. See
<citerefentry > <refentrytitle > systemd.journal-fields</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
for more information about the collected metadata.
</para>
2017-11-02 13:33:01 +03:00
<para > Log data collected by the journal is primarily text-based but can also include binary data where
2021-12-17 13:23:28 +03:00
necessary. Individual fields making up a log record stored in the journal may be up to 2⁶⁴-1 bytes in size.</para>
2017-11-02 13:33:01 +03:00
<para > The journal service stores log data either persistently below <filename > /var/log/journal</filename> or in a
volatile way below <filename > /run/log/journal/</filename> (in the latter case it is lost at reboot). By default, log
data is stored persistently if <filename > /var/log/journal/</filename> exists during boot, with an implicit fallback
to volatile storage otherwise. Use <varname > Storage=</varname> in
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> to configure
where log data is placed, independently of the existence of <filename > /var/log/journal/</filename> .</para>
2021-05-11 00:08:58 +03:00
<para > Note that journald will initially use volatile storage, until a call to
<command > journalctl --flush</command> (or sending <constant > SIGUSR1</constant> to journald) will cause
2021-05-03 18:08:25 +03:00
it to switch to persistent logging (under the conditions mentioned above). This is done automatically
on boot via <literal > systemd-journal-flush.service</literal> .</para>
2017-11-02 13:33:01 +03:00
<para > On systems where <filename > /var/log/journal/</filename> does not exist yet but where persistent logging is
desired (and the default <filename > journald.conf</filename> is used), it is sufficient to create the directory, and
ensure it has the correct access modes and ownership:</para>
2015-09-28 04:08:20 +03:00
<programlisting > mkdir -p /var/log/journal
systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
2015-02-04 05:14:13 +03:00
<para > See
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
for information about the configuration of this service.</para>
</refsect1>
2017-09-15 15:17:32 +03:00
<refsect1 >
<title > Stream logging</title>
<para > The systemd service manager invokes all service processes with standard output and standard error connected
to the journal by default. This behaviour may be altered via the
<varname > StandardOutput=</varname> /<varname > StandardError=</varname> unit file settings, see
<citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for details. The
journal converts the log byte stream received this way into individual log records, splitting the stream at newline
(<literal > \n</literal> , ASCII <constant > 10</constant> ) and <constant > NUL</constant> bytes.</para>
<para > If <filename > systemd-journald.service</filename> is stopped, the stream connections associated with all
services are terminated. Further writes to those streams by the service will result in <constant > EPIPE</constant>
errors. In order to react gracefully in this case it is recommended that programs logging to standard output/error
2017-10-10 22:59:03 +03:00
ignore such errors. If the <constant > SIGPIPE</constant> UNIX signal handler is not blocked or turned off, such
2017-09-15 15:17:32 +03:00
write attempts will also result in such process signals being generated, see
2020-06-25 15:37:24 +03:00
<citerefentry project= 'man-pages' > <refentrytitle > signal</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> .
To mitigate this issue, systemd service manager explicitly turns off the <constant > SIGPIPE</constant>
signal for all invoked processes by default (this may be changed for each unit individually via the
<varname > IgnoreSIGPIPE=</varname> option, see
2017-09-15 15:17:32 +03:00
<citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for
2020-06-25 15:37:24 +03:00
details). After the standard output/standard error streams have been terminated they may not be recovered
until the services they are associated with are restarted. Note that during normal operation,
<filename > systemd-journald.service</filename> stores copies of the file descriptors for those streams in
the service manager. If <filename > systemd-journald.service</filename> is restarted using
<command > systemctl restart</command> or equivalent operation instead of a pair of separate
<command > systemctl stop</command> and <command > systemctl start</command> commands (or equivalent
operations), these stream connections are not terminated and survive the restart. It is thus safe to
restart <filename > systemd-journald.service</filename> , but stopping it is not recommended.</para>
2017-09-15 15:17:32 +03:00
<para > Note that the log record metadata for records transferred via such standard output/error streams reflect the
metadata of the peer the stream was originally created for. If the stream connection is passed on to other
processes (such as further child processes forked off the main service process), the log records will not reflect
their metadata, but will continue to describe the original process. This is different from the other logging
transports listed above, which are inherently record based and where the metadata is always associated with the
individual record.</para>
2017-10-10 22:59:03 +03:00
<para > In addition to the implicit standard output/error logging of services, stream logging is also available
2017-09-15 15:17:32 +03:00
via the <citerefentry > <refentrytitle > systemd-cat</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> command
line tool.</para>
journald: make maximum size of stream log lines configurable and bump it to 48K (#6838)
This adds a new setting LineMax= to journald.conf, and sets it by
default to 48K. When we convert stream-based stdout/stderr logging into
record-based log entries, read up to the specified amount of bytes
before forcing a line-break.
This also makes three related changes:
- When a NUL byte is read we'll not recognize this as alternative line
break, instead of silently dropping everything after it. (see #4863)
- The reason for a line-break is now encoded in the log record, if it
wasn't a plain newline. Specifically, we distuingish "nul",
"line-max" and "eof", for line breaks due to NUL byte, due to the
maximum line length as configured with LineMax= or due to end of
stream. This data is stored in the new implicit _LINE_BREAK= field.
It's not synthesized for plain \n line breaks.
- A randomized 128bit ID is assigned to each log stream.
With these three changes in place it's (mostly) possible to reconstruct
the original byte streams from log data, as (most) of the context of
the conversion from the byte stream to log records is saved now. (So,
the only bits we still drop are empty lines. Which might be something to
look into in a future change, and which is outside of the scope of this
work)
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=86465
See: #4863
Replaces: #4875
2017-09-22 11:22:24 +03:00
<para > Currently, the number of parallel log streams <filename > systemd-journald</filename> will accept is limited to
2017-10-10 22:59:03 +03:00
4096. When this limit is reached further log streams may be established but will receive
journald: make maximum size of stream log lines configurable and bump it to 48K (#6838)
This adds a new setting LineMax= to journald.conf, and sets it by
default to 48K. When we convert stream-based stdout/stderr logging into
record-based log entries, read up to the specified amount of bytes
before forcing a line-break.
This also makes three related changes:
- When a NUL byte is read we'll not recognize this as alternative line
break, instead of silently dropping everything after it. (see #4863)
- The reason for a line-break is now encoded in the log record, if it
wasn't a plain newline. Specifically, we distuingish "nul",
"line-max" and "eof", for line breaks due to NUL byte, due to the
maximum line length as configured with LineMax= or due to end of
stream. This data is stored in the new implicit _LINE_BREAK= field.
It's not synthesized for plain \n line breaks.
- A randomized 128bit ID is assigned to each log stream.
With these three changes in place it's (mostly) possible to reconstruct
the original byte streams from log data, as (most) of the context of
the conversion from the byte stream to log records is saved now. (So,
the only bits we still drop are empty lines. Which might be something to
look into in a future change, and which is outside of the scope of this
work)
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=86465
See: #4863
Replaces: #4875
2017-09-22 11:22:24 +03:00
<constant > EPIPE</constant> right from the beginning.</para>
2017-09-15 15:17:32 +03:00
</refsect1>
2019-11-27 21:25:51 +03:00
<refsect1 >
<title > Journal Namespaces</title>
<para > Journal 'namespaces' are both a mechanism for logically isolating the log stream of projects
consisting of one or more services from the rest of the system and a mechanism for improving
performance. Multiple journal namespaces may exist simultaneously, each defining its own, independent log
stream managed by its own instance of <command > systemd-journald</command> . Namespaces are independent of
each other, both in the data store and in the IPC interface. By default only a single 'default' namespace
exists, managed by <filename > systemd-journald.service</filename> (and its associated socket
units). Additional namespaces are created by starting an instance of the
<filename > systemd-journald@.service</filename> service template. The instance name is the namespace
identifier, which is a short string used for referencing the journal namespace. Service units may be
assigned to a specific journal namespace through the <varname > LogNamespace=</varname> unit file setting,
see <citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for
details. The <option > --namespace=</option> switch of
<citerefentry > <refentrytitle > journalctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> may be
used to view the log stream of a specific namespace. If the switch is not used the log stream of the
default namespace is shown, i.e. log data from other namespaces is not visible.</para>
<para > Services associated with a specific log namespace may log via syslog, the native logging protocol
of the journal and via stdout/stderr; the logging from all three transports is associated with the
namespace.</para>
<para > By default only the default namespace will collect kernel and audit log messages.</para>
<para > The <command > systemd-journald</command> instance of the default namespace is configured through
<filename > /etc/systemd/journald.conf</filename> (see below), while the other instances are configured
through <filename > /etc/systemd/journald@<replaceable > NAMESPACE</replaceable> .conf</filename> . The journal
log data for the default namespace is placed in
<filename > /var/log/journal/<replaceable > MACHINE_ID</replaceable> </filename> (see below) while the data
for the other namespaces is located in
<filename > /var/log/journal/<replaceable > MACHINE_ID</replaceable> .<replaceable > NAMESPACE</replaceable> </filename> .</para>
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > Signals</title>
<variablelist >
<varlistentry >
<term > SIGUSR1</term>
2019-11-27 21:24:44 +03:00
<listitem > <para > Request that journal data from <filename > /run/</filename> is flushed to
<filename > /var/</filename> in order to make it persistent (if this is enabled). This must be used
2020-10-05 19:08:21 +03:00
after <filename > /var/</filename> is mounted, as otherwise log data from <filename > /run/</filename> is
never flushed to <filename > /var/</filename> regardless of the configuration. Use the
2019-11-27 21:24:44 +03:00
<command > journalctl --flush</command> command to request flushing of the journal files, and wait for
2015-11-11 14:59:09 +03:00
the operation to complete. See
2019-11-27 21:24:44 +03:00
<citerefentry > <refentrytitle > journalctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> for
2023-08-22 19:52:36 +03:00
details.</para>
<xi:include href= "version-info.xml" xpointer= "v186" /> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
<varlistentry >
<term > SIGUSR2</term>
2019-11-27 21:24:44 +03:00
<listitem > <para > Request immediate rotation of the journal files. Use the <command > journalctl
--rotate</command> command to request journal file rotation, and wait for the operation to
2023-08-22 19:52:36 +03:00
complete.</para>
<xi:include href= "version-info.xml" xpointer= "v186" /> </listitem>
2015-11-11 14:59:09 +03:00
</varlistentry>
<varlistentry >
<term > SIGRTMIN+1</term>
2019-11-27 21:24:44 +03:00
<listitem > <para > Request that all unwritten log data is written to disk. Use the <command > journalctl
--sync</command> command to trigger journal synchronization, and wait for the operation to
2023-08-22 19:52:36 +03:00
complete.</para>
<xi:include href= "version-info.xml" xpointer= "v228" /> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
</variablelist>
</refsect1>
2024-04-30 13:26:27 +03:00
<refsect1 >
<title > Credentials</title>
<para > <command > systemd-journald</command> supports the service credentials logic as implemented by
<varname > ImportCredential=</varname> /<varname > LoadCredential=</varname> /<varname > SetCredential=</varname>
(see <citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for
details). The following credentials are used when passed in:</para>
<variablelist class= 'system-credentials' >
<varlistentry >
<term > <varname > journal.forward_to_socket</varname> </term>
<listitem > <para > May contain a socket address to which logs should be forwarded. See
<varname > ForwardToSocket=</varname> in
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .</para>
<xi:include href= "version-info.xml" xpointer= "v256" /> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > journal.storage</varname> </term>
<listitem > <para > May be used to specify where journal files should be stored. See
<varname > Storage=</varname> in
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .</para>
<xi:include href= "version-info.xml" xpointer= "v256" /> </listitem>
</varlistentry>
</variablelist>
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > Kernel Command Line</title>
<para > A few configuration parameters from
<filename > journald.conf</filename> may be overridden on the kernel
command line:</para>
<variablelist class= 'kernel-commandline-options' >
<varlistentry >
<term > <varname > systemd.journald.forward_to_syslog=</varname> </term>
<term > <varname > systemd.journald.forward_to_kmsg=</varname> </term>
<term > <varname > systemd.journald.forward_to_console=</varname> </term>
<term > <varname > systemd.journald.forward_to_wall=</varname> </term>
<listitem > <para > Enables/disables forwarding of collected log
messages to syslog, the kernel log buffer, the system console
or wall.
</para>
<para > See
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
for information about these settings.</para>
2023-09-18 18:03:38 +03:00
<xi:include href= "version-info.xml" xpointer= "v186" />
2015-02-04 05:14:13 +03:00
</listitem>
</varlistentry>
2024-04-22 12:26:42 +03:00
<varlistentry >
<term > <varname > systemd.journald.max_level_store=</varname> </term>
<term > <varname > systemd.journald.max_level_syslog=</varname> </term>
<term > <varname > systemd.journald.max_level_kmsg=</varname> </term>
<term > <varname > systemd.journald.max_level_console=</varname> </term>
<term > <varname > systemd.journald.max_level_wall=</varname> </term>
<term > <varname > systemd.journald.max_level_socket=</varname> </term>
<listitem > <para > Controls the maximum log level of messages that are stored in the journal, forwarded
to syslog, kmsg, the console, the wall, or a socket. This kernel command line options override the
settings of the same names in the
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
file.</para>
<xi:include href= "version-info.xml" xpointer= "v232" />
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
</variablelist>
2019-11-27 21:25:51 +03:00
<para > Note that these kernel command line options are only honoured by the default namespace, see
above.</para>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 >
<title > Access Control</title>
<para > Journal files are, by default, owned and readable by the
<literal > systemd-journal</literal> system group but are not
2018-08-23 17:57:30 +03:00
writable. Adding a user to this group thus enables them to read
2015-02-04 05:14:13 +03:00
the journal files.</para>
2019-12-19 03:09:49 +03:00
<para > By default, each user, with a UID outside the range of system users,
dynamic service users, and the nobody user, will get their own set of
journal files in <filename > /var/log/journal/</filename> . See
<ulink url= "https://systemd.io/UIDS-GIDS" > Users, Groups, UIDs and GIDs on systemd systems</ulink>
for more details about UID ranges. These journal
2015-02-04 05:14:13 +03:00
files will not be owned by the user, however, in order to avoid
that the user can write to them directly. Instead, file system
ACLs are used to ensure the user gets read access only.</para>
<para > Additional users and groups may be granted access to journal
files via file system access control lists (ACL). Distributions
and administrators may choose to grant read access to all members
of the <literal > wheel</literal> and <literal > adm</literal> system
groups with a command such as the following:</para>
<programlisting > # setfacl -Rnm g:wheel:rx,d:g:wheel:rx,g:adm:rx,d:g:adm:rx /var/log/journal/</programlisting>
<para > Note that this command will update the ACLs both for
existing journal files and for future journal files created in the
<filename > /var/log/journal/</filename> directory.</para>
</refsect1>
<refsect1 >
<title > Files</title>
<variablelist >
<varlistentry >
2015-06-18 20:47:44 +03:00
<term > <filename > /etc/systemd/journald.conf</filename> </term>
2015-02-04 05:14:13 +03:00
2018-03-23 15:54:20 +03:00
<listitem > <para > Configure <command > systemd-journald</command> behavior. See
2015-02-04 05:14:13 +03:00
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
2023-08-22 19:52:36 +03:00
</para>
<xi:include href= "version-info.xml" xpointer= "v206" /> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
<varlistentry >
<term > <filename > /run/log/journal/<replaceable > machine-id</replaceable> /*.journal</filename> </term>
<term > <filename > /run/log/journal/<replaceable > machine-id</replaceable> /*.journal~</filename> </term>
<term > <filename > /var/log/journal/<replaceable > machine-id</replaceable> /*.journal</filename> </term>
<term > <filename > /var/log/journal/<replaceable > machine-id</replaceable> /*.journal~</filename> </term>
2018-03-23 15:54:20 +03:00
<listitem > <para > <command > systemd-journald</command> writes entries to files in
2015-02-04 05:14:13 +03:00
<filename > /run/log/journal/<replaceable > machine-id</replaceable> /</filename>
or
<filename > /var/log/journal/<replaceable > machine-id</replaceable> /</filename>
with the <literal > .journal</literal> suffix. If the daemon is
stopped uncleanly, or if the files are found to be corrupted,
they are renamed using the <literal > .journal~</literal>
suffix, and <command > systemd-journald</command> starts writing
2020-10-05 19:08:21 +03:00
to a new file. <filename > /run/</filename> is used when
2015-02-04 05:14:13 +03:00
<filename > /var/log/journal</filename> is not available, or
when <option > Storage=volatile</option> is set in the
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2018-03-23 15:54:20 +03:00
configuration file.</para>
<para > When <filename > systemd-journald</filename> ceases writing to a journal file,
it will be renamed to <literal > <replaceable > original-name</replaceable> @<replaceable > suffix.journal</replaceable> </literal>
(or <literal > <replaceable > original-name</replaceable> @<replaceable > suffix.journal~</replaceable> </literal> ).
Such files are "archived" and will not be written to any more.</para>
<para > In general, it is safe to read or copy any journal file (active or archived).
<citerefentry > <refentrytitle > journalctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
and the functions in the
<citerefentry > <refentrytitle > sd-journal</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
library should be able to read all entries that have been fully written.</para>
2018-03-23 16:04:13 +03:00
<para > <filename > systemd-journald</filename> will automatically remove the oldest
archived journal files to limit disk use. See <varname > SystemMaxUse=</varname>
and related settings in
<citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
2023-08-22 19:52:36 +03:00
</para>
<xi:include href= "version-info.xml" xpointer= "v206" /> </listitem>
2015-10-12 06:25:43 +03:00
</varlistentry>
<varlistentry >
<term > <filename > /dev/kmsg</filename> </term>
<term > <filename > /dev/log</filename> </term>
<term > <filename > /run/systemd/journal/dev-log</filename> </term>
<term > <filename > /run/systemd/journal/socket</filename> </term>
<term > <filename > /run/systemd/journal/stdout</filename> </term>
2019-11-27 21:25:51 +03:00
<listitem > <para > Sockets and other file node paths that <command > systemd-journald</command> will
listen on and are visible in the file system. In addition to these,
<command > systemd-journald</command> can listen for audit events using <citerefentry
2022-12-06 22:15:43 +03:00
project='man-pages'><refentrytitle > netlink</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ,
depending on whether <literal > systemd-journald-audit.socket</literal> is enabled or
2023-08-22 19:52:36 +03:00
not.</para>
<xi:include href= "version-info.xml" xpointer= "v228" /> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
</variablelist>
2019-11-27 21:25:51 +03:00
<para > If journal namespacing is used these paths are slightly altered to include a namespace identifier, see above.</para>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 >
<title > See Also</title>
2023-12-22 21:09:32 +03:00
<para > <simplelist type= "inline" >
<member > <citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> </member>
<member > <citerefentry > <refentrytitle > journalctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> </member>
<member > <citerefentry > <refentrytitle > journald.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> </member>
<member > <citerefentry > <refentrytitle > systemd.journal-fields</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> </member>
<member > <citerefentry > <refentrytitle > sd-journal</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> </member>
<member > <citerefentry > <refentrytitle > systemd-coredump</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> </member>
<member > <citerefentry project= 'man-pages' > <refentrytitle > setfacl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> </member>
<member > <citerefentry > <refentrytitle > sd_journal_print</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> </member>
<member > <command > pydoc systemd.journal</command> </member>
</simplelist> </para>
2015-02-04 05:14:13 +03:00
</refsect1>
2012-06-01 03:05:38 +04:00
</refentry>
