X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-journald.service.xml;h=d751f9b8551b38513e8446ab9a418a2b4bd8318a;hb=77a9e8de6572db6ba5ca49023937b67fc835f356;hp=3c71a59c954ce7b7f8332cce8b9458b90fa26619;hpb=a8eedf4953d379dc09ee2b04e69a0a54ba247a02;p=elogind.git
diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml
index 3c71a59c9..d751f9b85 100644
--- a/man/systemd-journald.service.xml
+++ b/man/systemd-journald.service.xml
@@ -46,7 +46,7 @@
systemd-journald.service
systemd-journald.socket
systemd-journald
- systemd Journal Service
+ Journal service
@@ -73,24 +73,24 @@
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
/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
the data.
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
+ 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.
See
@@ -111,13 +111,13 @@
is flushed to
/var/ in order to
make it persistent (if this is
- enabled). This may be used after
+ enabled). This must be used after
/var/ is mounted,
- but is generally not required since
- the first journal write when
- /var/ becomes
- writable triggers the flushing
- anyway.
+ as otherwise log data from
+ /run is never
+ flushed to /var
+ regardless of the
+ configuration.
@@ -134,10 +134,10 @@
Kernel Command Line
A few configuration parameters from
- journald.conf may be overriden on
+ journald.conf may be overridden on
the kernel command line:
-
+
systemd.journald.forward_to_syslog=
systemd.journald.forward_to_kmsg=
@@ -158,6 +158,38 @@
+
+ Access Control
+
+ Journal files are, by default, owned and readable
+ by the systemd-journal system group
+ 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
+ avoid that the user can write to them
+ directly. Instead, file system ACLs are used to ensure
+ the user gets read access only.
+
+ 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
+ wheel and adm
+ system groups with a command such as the
+ following:
+
+ # setfacl -Rnm g:wheel:rx,d:g:wheel:rx,g:adm:rx,d:g:adm:rx /var/log/journal/
+
+ Note that this command will update the ACLs both
+ for existing journal files and for future journal
+ files created in the
+ /var/log/journal/
+ directory.
+
See Also
@@ -166,7 +198,8 @@
journalctl1,
journald.conf5,
systemd.journal-fields7,
- sd-journal7
+ sd-journal3,
+ setfacl1