← Back to branch summary

~ubuntu-branches/ubuntu/trusty/systemd/trusty

« back to all changes in this revision

Viewing changes to man/systemd.journal-fields.html

Tags: upstream-202
Import upstream version 202

Show diffs side-by-side

added added

removed removed

Lines of Context:
man/systemd.journal-fields.html
2
2
  <a href="systemd.directives.html">Directives </a>·
3
3
  <a href="../python-systemd/index.html">Python </a>·
4
4
  <a href="../libudev/index.html">libudev </a>·
5
 
  <a href="../libudev/index.html">gudev </a><hr><div class="refentry"><a name="systemd.journal-fields"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>systemd.journal-fields — Special journal fields</p></div><div class="refsect1"><a name="idp125200"></a><h2>Description</h2><p>Entries in the journal resemble an environment
 
5
  <a href="../libudev/index.html">gudev </a><span style="float:right">systemd 202</span><hr><div class="refentry"><a name="systemd.journal-fields"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>systemd.journal-fields — Special journal fields</p></div><div class="refsect1"><a name="idp3742144"></a><h2>Description</h2><p>Entries in the journal resemble an environment
6
6
                block in their syntax, however with fields that can
7
7
                include binary data. Primarily, fields are formatted
8
8
                UTF-8 text strings, and binary formatting is used only
11
11
                applications, but a few fields have special
12
12
                meaning. All fields with special meanings are
13
13
                optional. In some cases fields may appear more than
14
 
                once per entry.</p></div><div class="refsect1"><a name="idp3964352"></a><h2>User Journal Fields</h2><p>User fields are fields that are directly passed
 
14
                once per entry.</p></div><div class="refsect1"><a name="idp3492592"></a><h2>User Journal Fields</h2><p>User fields are fields that are directly passed
15
15
                from clients and stored in the journal.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="varname">MESSAGE=</code></span></dt><dd><p>The human readable
16
16
                                        message string for this
17
17
                                        entry. This is supposed to be
57
57
                                        (formatted as decimal string),
58
58
                                        the identifier string
59
59
                                        (i.e. "tag"), and the client
60
 
                                        PID.</p></dd></dl></div></div><div class="refsect1"><a name="idp64640"></a><h2>Trusted Journal Fields</h2><p>Fields prefixed with an underscore are trusted
 
60
                                        PID.</p></dd></dl></div></div><div class="refsect1"><a name="idp222512"></a><h2>Trusted Journal Fields</h2><p>Fields prefixed with an underscore are trusted
61
61
                fields, i.e. fields that are implicitly added by the
62
62
                journal and cannot be altered by client code.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="varname">_PID=</code>, </span><span class="term"><code class="varname">_UID=</code>, </span><span class="term"><code class="varname">_GID=</code></span></dt><dd><p>The process, user and
63
63
                                        group ID of the process the
114
114
                                        standard output or error
115
115
                                        output, or for those read
116
116
                                        from the kernel, respectively.
117
 
                                        </p></dd></dl></div></div><div class="refsect1"><a name="idp5040864"></a><h2>Kernel Journal Fields</h2><p>Kernel fields are fields that are used by
 
117
                                        </p></dd></dl></div></div><div class="refsect1"><a name="idp67584"></a><h2>Kernel Journal Fields</h2><p>Kernel fields are fields that are used by
118
118
                messages originating in the kernel and stored in the
119
119
                journal.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="varname">_KERNEL_DEVICE=</code></span></dt><dd><p>The kernel device
120
120
                                        name. If the entry is
138
138
                                        pointing to the device node in
139
139
                                        <code class="filename">/dev</code>. This
140
140
                                        field is frequently set more
141
 
                                        than once per entry.</p></dd></dl></div></div><div class="refsect1"><a name="idp5054528"></a><h2>Special Journal Fields</h2><p>Fields used by the <span class="command"><strong>systemd-coredump</strong></span>
 
141
                                        than once per entry.</p></dd></dl></div></div><div class="refsect1"><a name="idp4762720"></a><h2>Special Journal Fields</h2><p>Fields used by the <span class="command"><strong>systemd-coredump</strong></span>
142
142
                coredump kernel helper.
143
143
                </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="varname">COREDUMP_UNIT=</code>, </span><span class="term"><code class="varname">COREDUMP_USER_UNIT=</code></span></dt><dd><p>Used to annotate
144
144
                                        messages containing coredumps from
145
145
                                        system and session units.
146
146
                                        See
147
147
                                        <a href="systemd-coredumpctl.html"><span class="citerefentry"><span class="refentrytitle">systemd-coredumpctl</span>(1)</span></a>.
148
 
                                        </p></dd></dl></div></div><div class="refsect1"><a name="idp5060128"></a><h2>Address Fields</h2><p>During serialization into external formats, such
 
148
                                        </p></dd></dl></div></div><div class="refsect1"><a name="idp4768320"></a><h2>Address Fields</h2><p>During serialization into external formats, such
149
149
                as the <a class="ulink" href="http://www.freedesktop.org/wiki/Software/systemd/export" target="_top">Journal
150
150
                Export Format</a> or the <a class="ulink" href="http://www.freedesktop.org/wiki/Software/systemd/json" target="_top">Journal
151
151
                JSON Format</a>, the addresses of journal entries
182
182
                                        address for the entry this
183
183
                                        should be combined with with
184
184
                                        boot ID in
185
 
                                        <code class="literal">_BOOT_ID=</code>.</p></dd></dl></div></div><div class="refsect1"><a name="idp5073504"></a><h2>See Also</h2><p>
 
185
                                        <code class="literal">_BOOT_ID=</code>.</p></dd></dl></div></div><div class="refsect1"><a name="idp4781696"></a><h2>See Also</h2><p>
186
186
                          <a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>,
187
187
                          <a href="journalctl.html"><span class="citerefentry"><span class="refentrytitle">journalctl</span>(1)</span></a>,
188
188
                          <a href="journald.conf.html"><span class="citerefentry"><span class="refentrytitle">journald.conf</span>(5)</span></a>,