Merging upstream version 4.23.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 64 insertions, 1 deletions

diff --git a/upstream/opensuse-tumbleweed/man7/systemd.journal-fields.7 b/upstream/opensuse-tumbleweed/man7/systemd.journal-fields.7
index 9bd44b20..161f42e3 100644
--- a/upstream/opensuse-tumbleweed/man7/systemd.journal-fields.7
+++ b/upstream/opensuse-tumbleweed/man7/systemd.journal-fields.7
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.JOURNAL\-FIELDS" "7" "" "systemd 254" "systemd.journal-fields"
+.TH "SYSTEMD\&.JOURNAL\-FIELDS" "7" "" "systemd 255" "systemd.journal-fields"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -57,6 +57,8 @@ The code location generating this message, if known\&. Contains the source filen
 The low\-level Unix error number causing this entry, if any\&. Contains the numeric value of
 \fBerrno\fR(3)
 formatted as a decimal string\&.
+.sp
+Added in version 188\&.
 .RE
 .PP
 \fIINVOCATION_ID=\fR, \fIUSER_INVOCATION_ID=\fR
@@ -64,6 +66,8 @@ formatted as a decimal string\&.
 A randomized, unique 128\-bit ID identifying each runtime cycle of the unit\&. This is different from
 \fI_SYSTEMD_INVOCATION_ID\fR
 in that it is only used for messages coming from systemd code (e\&.g\&. logs from the system/user manager or from forked processes performing systemd\-related setup)\&.
+.sp
+Added in version 245\&.
 .RE
 .PP
 \fISYSLOG_FACILITY=\fR, \fISYSLOG_IDENTIFIER=\fR, \fISYSLOG_PID=\fR, \fISYSLOG_TIMESTAMP=\fR
@@ -89,6 +93,8 @@ byte and anything after it is not included)\&. Thus, the original syslog line is
 \fISYSLOG_RAW=\fR
 or it can be recreated based on the stored priority and facility, timestamp, identifier, and the message payload in
 \fIMESSAGE=\fR\&.
+.sp
+Added in version 240\&.
 .RE
 .PP
 \fIDOCUMENTATION=\fR
@@ -103,11 +109,15 @@ will include a hyperlink to a URL specified this way in their output\&. Should b
 or
 "info:"
 URL\&.
+.sp
+Added in version 246\&.
 .RE
 .PP
 \fITID=\fR
 .RS 4
 The numeric thread ID (TID) the log message originates from\&.
+.sp
+Added in version 247\&.
 .RE
 .PP
 \fIUNIT=\fR, \fIUSER_UNIT=\fR
@@ -124,6 +134,8 @@ are used with
 or
 "USER_UNIT=\fIname\fR\&.service"
 will be generated\&.
+.sp
+Added in version 251\&.
 .RE
 .SH "TRUSTED JOURNAL FIELDS"
 .PP
@@ -149,6 +161,8 @@ The name, the executable path, and the command line of the process the journal e
 The effective
 \fBcapabilities\fR(7)
 of the process the journal entry originates from\&.
+.sp
+Added in version 206\&.
 .RE
 .PP
 \fI_AUDIT_SESSION=\fR, \fI_AUDIT_LOGINUID=\fR
@@ -188,6 +202,8 @@ The invocation ID for the runtime cycle of the unit the message was generated in
 \fI$INVOCATION_ID\fR
 (see
 \fBsystemd.exec\fR(5))\&.
+.sp
+Added in version 233\&.
 .RE
 .PP
 \fI_HOSTNAME=\fR
@@ -202,31 +218,43 @@ How the entry was received by the journal service\&. Valid transports are:
 \fBaudit\fR
 .RS 4
 for those read from the kernel audit subsystem
+.sp
+Added in version 227\&.
 .RE
 .PP
 \fBdriver\fR
 .RS 4
 for internally generated messages
+.sp
+Added in version 205\&.
 .RE
 .PP
 \fBsyslog\fR
 .RS 4
 for those received via the local syslog socket with the syslog protocol
+.sp
+Added in version 205\&.
 .RE
 .PP
 \fBjournal\fR
 .RS 4
 for those received via the native journal protocol
+.sp
+Added in version 205\&.
 .RE
 .PP
 \fBstdout\fR
 .RS 4
 for those read from a service\*(Aqs standard output or error output
+.sp
+Added in version 205\&.
 .RE
 .PP
 \fBkernel\fR
 .RS 4
 for those read from the kernel
+.sp
+Added in version 205\&.
 .RE
 .RE
 .PP
@@ -235,6 +263,8 @@ for those read from the kernel
 Only applies to
 "_TRANSPORT=stdout"
 records: specifies a randomized 128\-bit 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\&.
+.sp
+Added in version 235\&.
 .RE
 .PP
 \fI_LINE_BREAK=\fR
@@ -255,6 +285,8 @@ in
 (if this was the last log record of a stream and the stream ended without a final newline character), or
 \fBpid\-change\fR
 (if the process which generated the log output changed in the middle of a line)\&. Note that this record is not generated when a normal newline character was used for marking the log line end\&.
+.sp
+Added in version 235\&.
 .RE
 .PP
 \fI_NAMESPACE=\fR
@@ -264,6 +296,8 @@ If this file was written by a
 instance managing a journal namespace that is not the default, this field contains the namespace identifier\&. See
 \fBsystemd-journald.service\fR(8)
 for details about journal namespaces\&.
+.sp
+Added in version 245\&.
 .RE
 .PP
 \fI_RUNTIME_SCOPE=\fR
@@ -271,6 +305,8 @@ for details about journal namespaces\&.
 A string field that specifies the runtime scope in which the message was logged\&. If
 "initrd", the log message was processed while the system was running inside the initrd\&. If
 "system", the log message was generated after the system switched execution to the host root filesystem\&.
+.sp
+Added in version 252\&.
 .RE
 .SH "KERNEL JOURNAL FIELDS"
 .PP
@@ -286,29 +322,39 @@ and prefixed by
 "n"\&. For all other devices, this is the subsystem name prefixed by
 "+", followed by
 ":", followed by the kernel device name\&.
+.sp
+Added in version 189\&.
 .RE
 .PP
 \fI_KERNEL_SUBSYSTEM=\fR
 .RS 4
 The kernel subsystem name\&.
+.sp
+Added in version 189\&.
 .RE
 .PP
 \fI_UDEV_SYSNAME=\fR
 .RS 4
 The kernel device name as it shows up in the device tree below
 /sys/\&.
+.sp
+Added in version 189\&.
 .RE
 .PP
 \fI_UDEV_DEVNODE=\fR
 .RS 4
 The device node path of this device in
 /dev/\&.
+.sp
+Added in version 189\&.
 .RE
 .PP
 \fI_UDEV_DEVLINK=\fR
 .RS 4
 Additional symlink names pointing to the device node in
 /dev/\&. This field is frequently set more than once per entry\&.
+.sp
+Added in version 189\&.
 .RE
 .SH "FIELDS TO LOG ON BEHALF OF A DIFFERENT PROGRAM"
 .PP
@@ -322,6 +368,8 @@ coredump kernel helper:
 .RS 4
 Used to annotate messages containing coredumps from system and session units\&. See
 \fBcoredumpctl\fR(1)\&.
+.sp
+Added in version 198\&.
 .RE
 .PP
 Privileged programs (currently UID 0) may attach
@@ -333,6 +381,8 @@ to attach additional fields on behalf of the caller:
 \fIOBJECT_PID=\fR\fI\fIPID\fR\fR
 .RS 4
 PID of the program that this message pertains to\&.
+.sp
+Added in version 205\&.
 .RE
 .PP
 \fIOBJECT_UID=\fR, \fIOBJECT_GID=\fR, \fIOBJECT_COMM=\fR, \fIOBJECT_EXE=\fR, \fIOBJECT_CMDLINE=\fR, \fIOBJECT_AUDIT_SESSION=\fR, \fIOBJECT_AUDIT_LOGINUID=\fR, \fIOBJECT_SYSTEMD_CGROUP=\fR, \fIOBJECT_SYSTEMD_SESSION=\fR, \fIOBJECT_SYSTEMD_OWNER_UID=\fR, \fIOBJECT_SYSTEMD_UNIT=\fR, \fIOBJECT_SYSTEMD_USER_UNIT=\fR
@@ -354,6 +404,17 @@ These are additional fields added automatically by
 as described above, except that the process identified by
 \fIPID\fR
 is described, instead of the process which logged the message\&.
+.sp
+Added in version 205\&.
+.RE
+.PP
+\fIOBJECT_SYSTEMD_INVOCATION_ID=\fR
+.RS 4
+An additional field added automatically by
+\fBsystemd\-journald\fR\&. The meaning is mostly the same as
+\fI_SYSTEMD_INVOCATION_ID=\fR, with the difference described above\&.
+.sp
+Added in version 235\&.
 .RE
 .SH "ADDRESS FIELDS"
 .PP
@@ -386,6 +447,8 @@ The monotonic time (\fBCLOCK_MONOTONIC\fR) at the point in time the entry was re
 The sequence number (and associated sequence number ID) of this journal entry in the journal file it originates from\&. See
 \fBsd_journal_get_seqnum\fR(3)
 for details\&.
+.sp
+Added in version 254\&.
 .RE
 .SH "SEE ALSO"
 .PP