X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-journald.service.xml;h=7ac73ed66d821013250828eb2a3e73a198a9d732;hp=45091c62abb1804b02db4e911d6b6b54c17aec97;hb=03ee5c38cb0da193dd08733fb4c0c2809cee6a99;hpb=65cd79f7f574532e5f91d581aaff923c29655bbd diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index 45091c62a..7ac73ed66 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,17 @@ 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 + 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 - unfakeable way. See + call, from standard input and standard error of system + services or via its native API. It 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 +79,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 @@ -142,11 +144,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 @@ -206,11 +209,15 @@ + /run/log/journal/machine-id/*.journal + /run/log/journal/machine-id/*.journal~ /var/log/journal/machine-id/*.journal /var/log/journal/machine-id/*.journal~ systemd-journald writes entries to files in + /run/log/journal/machine-id/ + or /var/log/journal/machine-id/ with the .journal suffix. If the daemon is stopped @@ -219,7 +226,15 @@ using the .journal~ suffix, and systemd-journald - starts writing to a new file. + starts writing to a new + file. /run is + used when + /var/log/journal + is not available, or when + is + set in the + journald.conf5 + configuration file.