X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-journald.service.xml;h=fa6e97edf06263eea3faf169b66e9bba447c24eb;hb=9e7e440835c43d81ffdbc299d2c07daaa641ed50;hp=5634dd0a21c2b2089194372c74b2ec5cb9ff1202;hpb=d4d60b316914770e9e671122394f96521841eac7;p=elogind.git
diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml
index 5634dd0a2..fa6e97edf 100644
--- a/man/systemd-journald.service.xml
+++ b/man/systemd-journald.service.xml
@@ -45,6 +45,7 @@
systemd-journald.service
systemd-journald.socket
+ systemd-journald-dev-log.socket
systemd-journald
Journal service
@@ -52,6 +53,7 @@
systemd-journald.service
systemd-journald.socket
+ systemd-journald-dev-log.socket
/usr/lib/systemd/systemd-journald
@@ -59,17 +61,35 @@
Description
systemd-journald 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 the kernel, from user processes via the libc
- syslog3
- call, from STDOUT/STDERR of system services or via its
- native API. It will implicitly collect numerous meta
- data fields for each log messages in a secure and
+ 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:
+
+
+ Kernel log messages, via kmsg
+
+ Simple system log messages, via the
+ libc syslog3
+ call
+
+ Structured system log messages via the
+ native Journal API, see
+ sd_journal_print4
+
+ Standard output and
+ standard error of system
+ services
+
+ Audit records, via the audit subsystem
+
+
+ The daemon will implicitly collect numerous
+ metadata fields for each log messages in a secure and
unfakeable way. See
systemd.journal-fields7
- for more information about the collected meta data.
+ for more information about the collected metadata.
Log data collected by the journal is primarily
@@ -77,7 +97,7 @@
necessary. All objects stored in the journal can be up
to 2^64-1 bytes in size.
- By default the journal stores log data in
+ By default, the journal stores log data in
/run/log/journal/. Since
/run/ is volatile, log data is
lost at reboot. To make the data persistent, it
@@ -87,8 +107,7 @@
the data.
systemd-journald will
- forward all received log messages to the AF_UNIX
- SOCK_DGRAM socket
+ forward all received log messages to the AF_UNIX/SOCK_DGRAM socket
/run/systemd/journal/syslog, if it exists, which
may be used by Unix syslog daemons to process the data
further.
@@ -142,11 +161,12 @@
systemd.journald.forward_to_syslog=
systemd.journald.forward_to_kmsg=
systemd.journald.forward_to_console=
+ systemd.journald.forward_to_wall=
Enables/disables
forwarding of collected log messages
- to syslog, the kernel log buffer or
- the system console.
+ to syslog, the kernel log buffer, the
+ system console or wall.
See
@@ -245,7 +265,9 @@
journald.conf5,
systemd.journal-fields7,
sd-journal3,
+ systemd-coredump8,
setfacl1,
+ sd_journal_print4,
pydoc systemd.journal.