X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.journal-fields.xml;h=472a0855cd7764232fddd96005b72c3114b4bcef;hb=02ea24ca2a0aac854c4e9e7d712f6464c8b29e4a;hp=bb89ed58d333fb5014274f14396510bcf50fdd0c;hpb=8c9552c6b417c8dc8d66019bc8e412c8d736454d;p=elogind.git
diff --git a/man/systemd.journal-fields.xml b/man/systemd.journal-fields.xml
index bb89ed58d..472a0855c 100644
--- a/man/systemd.journal-fields.xml
+++ b/man/systemd.journal-fields.xml
@@ -156,7 +156,10 @@
(formatted as decimal string),
the identifier string
(i.e. "tag"), and the client
- PID.
+ PID. (Note that the tag is
+ usually derived from glibc's
+ program_invocation_short_name
+ variable, see program_invocation_short_name3.)
@@ -244,8 +247,8 @@
_SELINUX_CONTEXT=
The SELinux security
- context of the process the
- journal entry originates
+ context (label) of the process
+ the journal entry originates
from.
@@ -456,7 +459,7 @@
messages containing coredumps from
system and session units.
See
- systemd-coredumpctl1.
+ coredumpctl1.
@@ -529,7 +532,7 @@
JSON Format, the addresses of journal entries
are serialized into fields prefixed with double
underscores. Note that these are not proper fields when
- stored in the journal but for addressing meta data of
+ stored in the journal but for addressing metadata of
entries. They cannot be written as part of structured
log entries via calls such as
sd_journal_send3. They
@@ -594,7 +597,7 @@
journalctl1,
journald.conf5,
sd-journal3,
- systemd-coredumpctl1,
+ coredumpctl1,
systemd.directives7