chiark
/
gitweb
/
~ianmdlvl
/
elogind.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
update TODO
[elogind.git]
/
man
/
systemd.journal-fields.xml
diff --git
a/man/systemd.journal-fields.xml
b/man/systemd.journal-fields.xml
index bb89ed58d333fb5014274f14396510bcf50fdd0c..6eeb6e395d5b86b706daf662c2ed075b3f3bda42 100644
(file)
--- 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
(formatted as decimal string),
the identifier string
(i.e. "tag"), and the client
- PID.</para>
+ PID. (Note that the tag is
+ usually derived from glibc's
+ <varname>program_invocation_short_name</varname>
+ variable, see <citerefentry><refentrytitle>program_invocation_short_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>.)</para>
</listitem>
</varlistentry>
</listitem>
</varlistentry>
@@
-244,8
+247,8
@@
<term><varname>_SELINUX_CONTEXT=</varname></term>
<listitem>
<para>The SELinux security
<term><varname>_SELINUX_CONTEXT=</varname></term>
<listitem>
<para>The SELinux security
- context
of the process the
- journal entry originates
+ context
(label) of the process
+
the
journal entry originates
from.</para>
</listitem>
</varlistentry>
from.</para>
</listitem>
</varlistentry>
@@
-529,7
+532,7
@@
JSON Format</ulink>, the addresses of journal entries
are serialized into fields prefixed with double
underscores. Note that these are not proper fields when
JSON Format</ulink>, 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
<citerefentry><refentrytitle>sd_journal_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>. They
entries. They cannot be written as part of structured
log entries via calls such as
<citerefentry><refentrytitle>sd_journal_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>. They