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=2f877f565c5580999de9641789d4deaad53d6e24;hp=2860ae9769e02325f613d27e7eabc8d49068398e;hb=057d9ab8f016edfe692b7b3e84fdf6e0e000bacd;hpb=74d005783e355acc784d123024e33bbb66ef9ef1 diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index 2860ae976..2f877f565 100644 --- a/man/systemd-journald.service.xml +++ b/man/systemd-journald.service.xml @@ -73,14 +73,14 @@ Log data collected by the journal is primarily - text based but can also include binary data where + text-based but can also include binary data where 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 + /run/ is volatile, log data is + lost at reboot. To make the data persistent, it is sufficient to create /var/log/journal/ where systemd-journald will then store @@ -89,8 +89,8 @@ systemd-journald will 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 + /run/systemd/journal/syslog, if it exists, which + may be used by Unix syslog daemons to process the data further. See @@ -161,15 +161,15 @@ Access Control - Journal files are by default owned and readable + Journal files are, by default, owned and readable by the systemd-journal system group - (but not writable). Adding a user to this group thus + but are not writable. Adding a user to this group thus enables her/him to read the journal files. By default, each logged in user will get her/his own set of journal files in /var/log/journal/. These files - will not be owned by the user however, in order to + 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. @@ -191,6 +191,52 @@ directory. + + Files + + + + /etc/systemd/journald.conf + + Configure + systemd-journald + behaviour. See + journald.conf5. + + + + + /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 + uncleanly, or if the files are found + to be corrupted, they are renamed + using the .journal~ + suffix, and + systemd-journald + 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. + + + + + See Also @@ -199,7 +245,8 @@ journald.conf5, systemd.journal-fields7, sd-journal3, - setfacl1 + setfacl1, + pydoc systemd.journal.