timestamp of the message, if
any is known that is different
from the reception time of the
- journal. The time in usec
- since the epoch formatted as
- decimal string.</para>
+ journal. This is the time in
+ usec since the epoch UTC
+ formatted as decimal
+ string.</para>
</listitem>
</varlistentry>
originating host.</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>_TRANSPORT=</term>
+ <listitem>
+ <para>How the entry was
+ received by the journal
+ service. One of
+ <literal>driver</literal>,
+ <literal>syslog</literal>,
+ <literal>journal</literal>,
+ <literal>stdout</literal>,
+ <literal>kernel</literal> for
+ internally generated messages,
+ for those received via the
+ local syslog socket with the
+ syslog protocol, for those
+ received via the native
+ journal protocol, for the
+ those read from a services'
+ standard output or error
+ output, resp. for those read
+ from the kernel.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
</refsect1>
<para>The wallclock time
(CLOCK_REALTIME) at the point
in time the entry was received
- by the journal. This has
+ by the journal, in usec since
+ the epoch UTC formatted as
+ decimal string. This has
different properties from
<literal>_SOURCE_REALTIME_TIMESTAMP=</literal>
as it is usually a bit later
<para>The monotonic time
(CLOCK_MONOTONIC) at the point
in time the entry was received
- by the journal. To be useful
- as an address for the entry
- this should be combined with
- with boot ID in
+ by the journal in usec
+ formatted as decimal
+ string. To be useful as an
+ address for the entry this
+ should be combined with with
+ boot ID in
<literal>_BOOT_ID=</literal>.</para>
</listitem>
</varlistentry>