X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=man%2Fsystemd.journal-fields.xml;h=e3d421c17866b45f7809dc8bce4087da5946aae9;hb=0307f79171ed47b120afcd432d1f463904ae515a;hp=b08ef1777e40980fa227b8fd1fcc92ab4c27c724;hpb=3219f05c1d55fa8264cbf136a63e1e10d080cb90;p=thirdparty%2Fsystemd.git diff --git a/man/systemd.journal-fields.xml b/man/systemd.journal-fields.xml index b08ef1777e4..e3d421c1786 100644 --- a/man/systemd.journal-fields.xml +++ b/man/systemd.journal-fields.xml @@ -1,42 +1,13 @@ - - + systemd.journal-fields systemd - - - - Developer - Lennart - Poettering - lennart@poettering.net - - @@ -82,14 +53,10 @@ MESSAGE_ID= - A 128-bit message identifier ID for recognizing - certain message types, if this is desirable. This should - contain a 128-bit ID formatted as a lower-case hexadecimal - string, without any separating dashes or suchlike. This is - recommended to be a UUID-compatible ID, but this is not - enforced, and formatted differently. Developers can generate - a new ID for this purpose with journalctl - . + A 128-bit message identifier ID for recognizing certain message types, if this is desirable. This + should contain a 128-bit ID formatted as a lower-case hexadecimal string, without any separating dashes or + suchlike. This is recommended to be a UUID-compatible ID, but this is not enforced, and formatted + differently. Developers can generate a new ID for this purpose with systemd-id128 new. @@ -129,16 +96,34 @@ SYSLOG_FACILITY= SYSLOG_IDENTIFIER= SYSLOG_PID= + SYSLOG_TIMESTAMP= - Syslog compatibility fields containing the facility - (formatted as decimal string), the identifier string (i.e. - "tag"), and the client PID. (Note that the tag is usually - derived from glibc's - program_invocation_short_name variable, - see + Syslog compatibility fields containing the facility (formatted as + decimal string), the identifier string (i.e. "tag"), the client PID, and + the timestamp as specified in the original datagram. (Note that the tag is + usually derived from glibc's + program_invocation_short_name variable, see program_invocation_short_name3.) + + + SYSLOG_RAW= + + The original contents of the syslog line as received in the syslog + datagram. This field is only included if the MESSAGE= + field was modified compared to the original payload or the timestamp could + not be located properly and is not included in + SYSLOG_TIMESTAMP=. Message truncation occurs when when + the message contains leading or trailing whitespace (trailing and leading + whitespace is stripped), or it contains an embedded + NUL byte (the NUL byte and + anything after it is not included). Thus, the original syslog line is + either stored as SYSLOG_RAW= or it can be recreated + based on the stored priority and facility, timestamp, identifier, and the + message payload in MESSAGE=. + + @@ -339,7 +324,7 @@ _STREAM_ID= - Only applies to _TRANSPORT=stream records: specifies a randomized 128bit ID assigned + Only applies to _TRANSPORT=stdout records: specifies a randomized 128bit ID assigned to the stream connection when it was first created. This ID is useful to reconstruct individual log streams from the log records: all log records carrying the same stream ID originate from the same stream. @@ -347,7 +332,7 @@ _LINE_BREAK= - Only applies to _TRANSPORT=stream records: indicates that the log message in the + Only applies to _TRANSPORT=stdout records: indicates that the log message in the standard output/error stream was not terminated with a normal newline character (\n, i.e. ASCII 10). Specifically, when set this field is one of (in case the line was terminated by a NUL byte), (in case the maximum log line length was reached, as