Adding upstream version 4.23.0.upstream/4.23.0

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

1 files changed, 247 insertions, 20 deletions

diff --git a/upstream/opensuse-tumbleweed/man5/systemd.unit.5 b/upstream/opensuse-tumbleweed/man5/systemd.unit.5
index 7d7946c8..9c3e27c6 100644
--- a/upstream/opensuse-tumbleweed/man5/systemd.unit.5
+++ b/upstream/opensuse-tumbleweed/man5/systemd.unit.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.UNIT" "5" "" "systemd 254" "systemd.unit"
+.TH "SYSTEMD\&.UNIT" "5" "" "systemd 255" "systemd.unit"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -738,6 +738,8 @@ may use this string as a noun in status messages ("Starting \fIdescription\fR\&.
 "exiting the container"
 or
 "updating the database once per day\&."\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIDocumentation=\fR
@@ -749,6 +751,8 @@ A space\-separated list of URIs referencing documentation for this unit or its c
 "info:",
 "man:"\&. For more information about the syntax of these URIs, see
 \fBuri\fR(7)\&. The URIs should be listed in order of relevance, starting with the most relevant\&. It is a good idea to first reference documentation that explains what the unit\*(Aqs purpose is, followed by how it is configured, followed by any other related documentation\&. This option may be specified more than once, in which case the specified list of URIs is merged\&. If the empty string is assigned to this option, the list is reset and all prior assignments will have no effect\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIWants=\fR
@@ -775,6 +779,8 @@ or
 \fIBefore=\fR, then both units will be started simultaneously and without any delay between them if
 foo\&.service
 is activated\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIRequires=\fR
@@ -806,6 +812,8 @@ dependency\&. Use the
 dependency type together with
 \fIAfter=\fR
 to ensure that a unit may never be in active state without a specific other unit also in active state (see below)\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIRequisite=\fR
@@ -825,6 +833,8 @@ in property listing of
 b\&.service\&.
 \fIRequisiteOf=\fR
 dependency cannot be specified directly\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIBindsTo=\fR
@@ -854,6 +864,8 @@ in property listing of
 b\&.service\&.
 \fIBoundBy=\fR
 dependency cannot be specified directly\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIPartOf=\fR
@@ -870,6 +882,8 @@ in property listing of
 b\&.service\&.
 \fIConsistsOf=\fR
 dependency cannot be specified directly\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIUpholds=\fR
@@ -892,6 +906,8 @@ a\&.service, this dependency will show as
 \fIUpheldBy=a\&.service\fR
 in the property listing of
 b\&.service\&.
+.sp
+Added in version 249\&.
 .RE
 .PP
 \fIConflicts=\fR
@@ -913,6 +929,8 @@ dependency must be declared\&. It doesn\*(Aqt matter which of the two ordering d
 below\&.
 .sp
 If unit A that conflicts with unit B is scheduled to be started at the same time as B, the transaction will either fail (in case both are required parts of the transaction) or be modified to be fixed (in case one or both jobs are not a required part of the transaction)\&. In the latter case, the job that is not required will be removed, or in case both are not required, the unit that conflicts will be started and the unit that is conflicted is stopped\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIBefore=\fR, \fIAfter=\fR
@@ -961,6 +979,8 @@ options, in which case the unit listed will be started before the unit that is c
 Note that
 \fIBefore=\fR
 dependencies on device units have no effect and are not supported\&. Devices generally become available as a result of an external hotplug event, and systemd creates the corresponding device unit without delay\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIOnFailure=\fR
@@ -968,6 +988,8 @@ dependencies on device units have no effect and are not supported\&. Devices gen
 A space\-separated list of one or more units that are activated when this unit enters the
 "failed"
 state\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIOnSuccess=\fR
@@ -975,22 +997,30 @@ state\&.
 A space\-separated list of one or more units that are activated when this unit enters the
 "inactive"
 state\&.
+.sp
+Added in version 249\&.
 .RE
 .PP
 \fIPropagatesReloadTo=\fR, \fIReloadPropagatedFrom=\fR
 .RS 4
 A space\-separated list of one or more units to which reload requests from this unit shall be propagated to, or units from which reload requests shall be propagated to this unit, respectively\&. Issuing a reload request on a unit will automatically also enqueue reload requests on all units that are linked to it using these two settings\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIPropagatesStopTo=\fR, \fIStopPropagatedFrom=\fR
 .RS 4
 A space\-separated list of one or more units to which stop requests from this unit shall be propagated to, or units from which stop requests shall be propagated to this unit, respectively\&. Issuing a stop request on a unit will automatically also enqueue stop requests on all units that are linked to it using these two settings\&.
+.sp
+Added in version 249\&.
 .RE
 .PP
 \fIJoinsNamespaceOf=\fR
 .RS 4
-For units that start processes (such as service units), lists one or more other units whose network and/or temporary file namespace to join\&. If this is specified on a unit (say, a\&.service has
-\fIJoinsNamespaceOf=b\&.service\fR), then this the inverse dependency (\fIJoinsNamespaceOf=a\&.service\fR
+For units that start processes (such as service units), lists one or more other units whose network and/or temporary file namespace to join\&. If this is specified on a unit (say,
+a\&.service
+has
+\fIJoinsNamespaceOf=b\&.service\fR), then the inverse dependency (\fIJoinsNamespaceOf=a\&.service\fR
 for b\&.service) is implied\&. This only applies to unit types which support the
 \fIPrivateNetwork=\fR,
 \fINetworkNamespacePath=\fR,
@@ -1007,6 +1037,8 @@ for details)\&. If a unit that has this setting set is started, its processes wi
 and/or
 \fIPrivateTmp=\fR
 is enabled for both the unit that joins the namespace and the unit whose namespace is joined\&.
+.sp
+Added in version 209\&.
 .RE
 .PP
 \fIRequiresMountsFor=\fR
@@ -1021,6 +1053,8 @@ Mount points marked with
 \fBnoauto\fR
 are not mounted automatically through
 local\-fs\&.target, but are still honored for the purposes of this option, i\&.e\&. they will be pulled in by this unit\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIOnSuccessJobMode=\fR, \fIOnFailureJobMode=\fR
@@ -1042,6 +1076,8 @@ will be enqueued\&. See
 option for details on the possible values\&. If this is set to
 "isolate", only a single unit may be listed in
 \fIOnSuccess=\fR/\fIOnFailure=\fR\&.
+.sp
+Added in version 209\&.
 .RE
 .PP
 \fIIgnoreOnIsolate=\fR
@@ -1052,6 +1088,8 @@ Takes a boolean argument\&. If
 for service, target, socket, timer, and path units, and
 \fBtrue\fR
 for slice, scope, device, swap, mount, and automount units\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIStopWhenUnneeded=\fR
@@ -1059,6 +1097,8 @@ for slice, scope, device, swap, mount, and automount units\&.
 Takes a boolean argument\&. If
 \fBtrue\fR, this unit will be stopped when it is no longer used\&. Note that, in order to minimize the work to be executed, systemd will not stop units by default unless they are conflicting with other units, or the user explicitly requested their shut down\&. If this option is set, a unit will be automatically cleaned up if no other active unit requires it\&. Defaults to
 \fBfalse\fR\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIRefuseManualStart=\fR, \fIRefuseManualStop=\fR
@@ -1066,6 +1106,8 @@ Takes a boolean argument\&. If
 Takes a boolean argument\&. If
 \fBtrue\fR, this unit can only be activated or deactivated indirectly\&. In this case, explicit start\-up or termination requested by the user is denied, however if it is started or stopped as a dependency of another unit, start\-up or termination will succeed\&. This is mostly a safety feature to ensure that the user does not accidentally activate units that are not intended to be activated explicitly, and not accidentally deactivate units that are not intended to be deactivated\&. These options default to
 \fBfalse\fR\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIAllowIsolate=\fR
@@ -1075,6 +1117,8 @@ Takes a boolean argument\&. If
 \fBsystemctl isolate\fR
 command\&. Otherwise, this will be refused\&. It probably is a good idea to leave this disabled except for target units that shall be used similar to runlevels in SysV init systems, just as a precaution to avoid unusable system states\&. This option defaults to
 \fBfalse\fR\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIDefaultDependencies=\fR
@@ -1083,6 +1127,24 @@ Takes a boolean argument\&. If
 \fByes\fR, (the default), a few default dependencies will implicitly be created for the unit\&. The actual dependencies created depend on the unit type\&. For example, for service units, these dependencies ensure that the service is started only after basic system initialization is completed and is properly terminated on system shutdown\&. See the respective man pages for details\&. Generally, only services involved with early boot or late shutdown should set this option to
 \fBno\fR\&. It is highly recommended to leave this option enabled for the majority of common units\&. If set to
 \fBno\fR, this option does not disable all implicit dependencies, just non\-essential ones\&.
+.sp
+Added in version 201\&.
+.RE
+.PP
+\fISurviveFinalKillSignal=\fR
+.RS 4
+Takes a boolean argument\&. Defaults to
+\fBno\fR\&. If
+\fByes\fR, processes belonging to this unit will not be sent the final
+"SIGTERM"
+and
+"SIGKILL"
+signals during the final phase of the system shutdown process\&. This functionality replaces the older mechanism that allowed a program to set
+"argv[0][0] = \*(Aq@\*(Aq"
+as described at
+\m[blue]\fBsystemd and Storage Daemons for the Root File System\fR\m[]\&\s-2\u[2]\d\s+2, which however continues to be supported\&.
+.sp
+Added in version 255\&.
 .RE
 .PP
 \fICollectMode=\fR
@@ -1109,6 +1171,8 @@ state, and thus an explicitly resetting of the
 \fBfailed\fR
 state is not necessary\&. Note that if this mode is used unit results (such as exit codes, exit signals, consumed resources, \&...) are flushed out immediately after the unit completed, except for what is stored in the logging subsystem\&. Defaults to
 \fBinactive\fR\&.
+.sp
+Added in version 236\&.
 .RE
 .PP
 \fIFailureAction=\fR, \fISuccessAction=\fR
@@ -1177,6 +1241,8 @@ is used by default the exit status of the main process of the unit (if this appl
 will trigger a userspace reboot operation\&.
 \fBsoft\-reboot\-force\fR
 does that too, but does not go through the shutdown transaction beforehand\&.
+.sp
+Added in version 236\&.
 .RE
 .PP
 \fIFailureActionExitStatus=\fR, \fISuccessActionExitStatus=\fR
@@ -1188,6 +1254,8 @@ are set to
 or
 \fBexit\-force\fR
 and the action is triggered\&. By default the exit status of the main process of the triggering unit (if this applies) is propagated\&. Takes a value in the range 0\&...255 or the empty string to request default behaviour\&.
+.sp
+Added in version 240\&.
 .RE
 .PP
 \fIJobTimeoutSec=\fR, \fIJobRunningTimeoutSec=\fR
@@ -1210,6 +1278,8 @@ defaults to
 Note: these timeouts are independent from any unit\-specific timeouts (for example, the timeout set with
 \fITimeoutStartSec=\fR
 in service units)\&. The job timeout has no effect on the unit itself\&. Or in other words: unit\-specific timeouts are useful to abort unit state changes, and revert them\&. The job timeout set with this option however is useful to abort only the job waiting for the unit state to change\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIJobTimeoutAction=\fR, \fIJobTimeoutRebootArgument=\fR
@@ -1227,6 +1297,8 @@ above\&. It takes the same values as
 configures an optional reboot string to pass to the
 \fBreboot\fR(2)
 system call\&.
+.sp
+Added in version 240\&.
 .RE
 .PP
 \fIStartLimitIntervalSec=\fR\fI\fIinterval\fR\fR, \fIStartLimitBurst=\fR\fI\fIburst\fR\fR
@@ -1243,7 +1315,9 @@ to configure how many starts per interval are allowed\&.
 .sp
 \fIinterval\fR
 is a time span with the default unit of seconds, but other units may be specified, see
-\fBsystemd.time\fR(5)\&. Defaults to
+\fBsystemd.time\fR(5)\&. The special value
+"infinity"
+can be used to limit the total number of start attempts, even if they happen at large time intervals\&. Defaults to
 \fIDefaultStartLimitIntervalSec=\fR
 in manager configuration file, and may be set to 0 to disable any kind of rate limiting\&.
 \fIburst\fR
@@ -1268,6 +1342,8 @@ will cause the restart rate counter for a service to be flushed, which is useful
 When a unit is unloaded due to the garbage collection logic (see above) its rate limit counters are flushed out too\&. This means that configuring start rate limiting for a unit that is not referenced continuously has no effect\&.
 .sp
 This setting does not apply to slice, target, device, and scope units, since they are unit types whose activation may either never fail, or may succeed only a single time\&.
+.sp
+Added in version 229\&.
 .RE
 .PP
 \fIStartLimitAction=\fR
@@ -1282,6 +1358,8 @@ settings\&. If
 \fBnone\fR
 is set, hitting the rate limit will trigger no action except that the start will not be permitted\&. Defaults to
 \fBnone\fR\&.
+.sp
+Added in version 229\&.
 .RE
 .PP
 \fIRebootArgument=\fR
@@ -1295,11 +1373,15 @@ or
 is a reboot action\&. This works just like the optional argument to
 \fBsystemctl reboot\fR
 command\&.
+.sp
+Added in version 229\&.
 .RE
 .PP
 \fISourcePath=\fR
 .RS 4
 A path to a configuration file this unit has been generated from\&. This is primarily useful for implementation of generator tools that convert configuration from an external configuration file format into native unit files\&. This functionality should not be used in normal units\&.
+.sp
+Added in version 201\&.
 .RE
 .SS "Conditions and Asserts"
 .PP
@@ -1372,6 +1454,8 @@ and is thus subject to
 setting in the same unit file has no effect on this condition\&. A special architecture name
 "native"
 is mapped to the architecture the system manager itself is compiled for\&. The test may be negated by prepending an exclamation mark\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIConditionFirmware=\fR
@@ -1451,6 +1535,8 @@ is the expected value of the SMBIOS field value (possibly containing shell style
 "$="/"!$="
 is used)\&.
 .RE
+.sp
+Added in version 249\&.
 .RE
 .PP
 \fIConditionVirtualization=\fR
@@ -1491,6 +1577,8 @@ to test against a specific implementation, or
 to check whether we are running in a user namespace\&. See
 \fBsystemd-detect-virt\fR(1)
 for a full list of known virtualization technologies and their identifiers\&. If multiple virtualization technologies are nested, only the innermost is considered\&. The test may be negated by prepending an exclamation mark\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionHost=\fR
@@ -1499,6 +1587,8 @@ for a full list of known virtualization technologies and their identifiers\&. If
 may be used to match against the hostname or machine ID of the host\&. This either takes a hostname string (optionally with shell style globs) which is tested against the locally set hostname as returned by
 \fBgethostname\fR(2), or a machine ID formatted as string (see
 \fBmachine-id\fR(5))\&. The test may be negated by prepending an exclamation mark\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionKernelCommandLine=\fR
@@ -1510,6 +1600,8 @@ may be used to check whether a specific kernel command line option is set (or if
 PID 1
 is used instead (i\&.e\&.
 /proc/1/cmdline)\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionKernelVersion=\fR
@@ -1535,16 +1627,20 @@ for a shell\-style glob match\&. If no operator is specified,
 is implied\&.
 .sp
 Note that using the kernel version string is an unreliable way to determine which features are supported by a kernel, because of the widespread practice of backporting drivers, features, and fixes from newer upstream kernels into older versions provided by distributions\&. Hence, this check is inherently unportable and should not be used for units which may be used on different distributions\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionCredential=\fR
 .RS 4
 \fIConditionCredential=\fR
 may be used to check whether a credential by the specified name was passed into the service manager\&. See
-\m[blue]\fBSystem and Service Credentials\fR\m[]\&\s-2\u[2]\d\s+2
+\m[blue]\fBSystem and Service Credentials\fR\m[]\&\s-2\u[3]\d\s+2
 for details about credentials\&. If used in services for the system service manager this may be used to conditionalize services based on system credentials passed in\&. If used in services for the per\-user service manager this may be used to conditionalize services based on credentials passed into the
 unit@\&.service
 service instance belonging to the user\&. The argument must be a valid credential name\&.
+.sp
+Added in version 252\&.
 .RE
 .PP
 \fIConditionEnvironment=\fR
@@ -1554,22 +1650,94 @@ may be used to check whether a specific environment variable is set (or if prefi
 \fIEnvironment=\fR
 or
 \fIEnvironmentFile=\fR, as described above\&. This is particularly useful when the service manager runs inside a containerized environment or as per\-user service manager, in order to check for variables passed in by the enclosing container manager or PAM\&.
+.sp
+Added in version 246\&.
 .RE
 .PP
 \fIConditionSecurity=\fR
 .RS 4
 \fIConditionSecurity=\fR
-may be used to check whether the given security technology is enabled on the system\&. Currently, the recognized values are
-"selinux",
-"apparmor",
-"tomoyo",
-"ima",
-"smack",
-"audit",
-"uefi\-secureboot",
-"tpm2"
-and
-"cvm"\&. The test may be negated by prepending an exclamation mark\&.
+may be used to check whether the given security technology is enabled on the system\&. Currently, the following values are recognized:
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.B Table\ \&3.\ \&Recognized security technologies
+.TS
+allbox tab(:);
+lB lB.
+T{
+Value
+T}:T{
+Description
+T}
+.T&
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l.
+T{
+selinux
+T}:T{
+SELinux MAC
+T}
+T{
+apparmor
+T}:T{
+AppArmor MAC
+T}
+T{
+tomoyo
+T}:T{
+Tomoyo MAC
+T}
+T{
+smack
+T}:T{
+SMACK MAC
+T}
+T{
+ima
+T}:T{
+Integrity Measurement Architecture (IMA)
+T}
+T{
+audit
+T}:T{
+Linux Audit Framework
+T}
+T{
+uefi\-secureboot
+T}:T{
+UEFI SecureBoot
+T}
+T{
+tpm2
+T}:T{
+Trusted Platform Module 2\&.0 (TPM2)
+T}
+T{
+cvm
+T}:T{
+Confidential virtual machine (SEV/TDX)
+T}
+T{
+measured\-uki
+T}:T{
+Unified Kernel Image with PCR 11 Measurements, as per \fBsystemd-stub\fR(7)\&. Added in version 255\&.
+T}
+.TE
+.sp 1
+The test may be negated by prepending an exclamation mark\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionCapability=\fR
@@ -1578,6 +1746,8 @@ Check whether the given capability exists in the capability bounding set of the
 \fBcapabilities\fR(7)
 for details)\&. Pass a capability name such as
 "CAP_MKNOD", possibly prefixed with an exclamation mark to negate the check\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionACPower=\fR
@@ -1585,6 +1755,8 @@ for details)\&. Pass a capability name such as
 Check whether the system has AC power, or is exclusively battery powered at the time of activation of the unit\&. This takes a boolean argument\&. If set to
 "true", the condition will hold only if at least one AC connector of the system is connected to a power source, or if no AC connectors are known\&. Conversely, if set to
 "false", the condition will hold only if there is at least one AC connector known and all AC connectors are disconnected from a power source\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionNeedsUpdate=\fR
@@ -1625,6 +1797,8 @@ Also note that if the update method includes a call to execute appropriate post\
 /usr/\&. In a typical distribution packaging scheme, packages will do any required update steps as part of the installation or upgrade, to make package contents immediately usable\&.
 \fIConditionNeedsUpdate=\fR
 should be used with other update mechanisms where such an immediate update does not happen\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionFirstBoot=\fR
@@ -1650,6 +1824,8 @@ If the
 option is specified on the kernel command line (taking a boolean), it will override the result of this condition check, taking precedence over
 /etc/machine\-id
 existence checks\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionPathExists=\fR
@@ -1657,6 +1833,8 @@ existence checks\&.
 Check for the existence of a file\&. If the specified absolute path name does not exist, the condition will fail\&. If the absolute path name passed to
 \fIConditionPathExists=\fR
 is prefixed with an exclamation mark ("!"), the test is negated, and the unit is only started if the path does not exist\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionPathExistsGlob=\fR
@@ -1664,6 +1842,8 @@ is prefixed with an exclamation mark ("!"), the test is negated, and the unit is
 \fIConditionPathExistsGlob=\fR
 is similar to
 \fIConditionPathExists=\fR, but checks for the existence of at least one file or directory matching the specified globbing pattern\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionPathIsDirectory=\fR
@@ -1672,6 +1852,8 @@ is similar to
 is similar to
 \fIConditionPathExists=\fR
 but verifies that a certain path exists and is a directory\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionPathIsSymbolicLink=\fR
@@ -1680,6 +1862,8 @@ but verifies that a certain path exists and is a directory\&.
 is similar to
 \fIConditionPathExists=\fR
 but verifies that a certain path exists and is a symbolic link\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionPathIsMountPoint=\fR
@@ -1688,6 +1872,8 @@ but verifies that a certain path exists and is a symbolic link\&.
 is similar to
 \fIConditionPathExists=\fR
 but verifies that a certain path exists and is a mount point\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionPathIsReadWrite=\fR
@@ -1696,6 +1882,8 @@ but verifies that a certain path exists and is a mount point\&.
 is similar to
 \fIConditionPathExists=\fR
 but verifies that the underlying file system is readable and writable (i\&.e\&. not mounted read\-only)\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionPathIsEncrypted=\fR
@@ -1704,6 +1892,8 @@ but verifies that the underlying file system is readable and writable (i\&.e\&.
 is similar to
 \fIConditionPathExists=\fR
 but verifies that the underlying file system\*(Aqs backing block device is encrypted using dm\-crypt/LUKS\&. Note that this check does not cover ext4 per\-directory encryption, and only detects block level encryption\&. Moreover, if the specified path resides on a file system on top of a loopback block device, only encryption above the loopback device is detected\&. It is not detected whether the file system backing the loopback block device is encrypted\&.
+.sp
+Added in version 246\&.
 .RE
 .PP
 \fIConditionDirectoryNotEmpty=\fR
@@ -1712,6 +1902,8 @@ but verifies that the underlying file system\*(Aqs backing block device is encry
 is similar to
 \fIConditionPathExists=\fR
 but verifies that a certain path exists and is a non\-empty directory\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionFileNotEmpty=\fR
@@ -1720,6 +1912,8 @@ but verifies that a certain path exists and is a non\-empty directory\&.
 is similar to
 \fIConditionPathExists=\fR
 but verifies that a certain path exists and refers to a regular file with a non\-zero size\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionFileIsExecutable=\fR
@@ -1728,6 +1922,8 @@ but verifies that a certain path exists and refers to a regular file with a non\
 is similar to
 \fIConditionPathExists=\fR
 but verifies that a certain path exists, is a regular file, and marked executable\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionUser=\fR
@@ -1738,6 +1934,8 @@ takes a numeric
 "@system"\&. This condition may be used to check whether the service manager is running as the given user\&. The special value
 "@system"
 can be used to check if the user id is within the system user range\&. This option is not useful for system services, as the system manager exclusively runs as the root user, and thus the test result is constant\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionGroup=\fR
@@ -1747,6 +1945,8 @@ is similar to
 \fIConditionUser=\fR
 but verifies that the service manager\*(Aqs real or effective group, or any of its auxiliary groups, match the specified group or GID\&. This setting does not support the special value
 "@system"\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionControlGroupController=\fR
@@ -1772,6 +1972,8 @@ will pass if the unified v2 cgroup hierarchy is used, and
 will pass if the legacy v1 hierarchy or the hybrid hierarchy are used\&. Note that legacy or hybrid hierarchies have been deprecated\&. See
 \fBsystemd\fR(1)
 for more information\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionMemory=\fR
@@ -1787,6 +1989,8 @@ Verify that the specified amount of system memory is available to the current sy
 "<>"),
 ">=",
 ">"\&. On bare\-metal systems compares the amount of physical memory in the system with the specified size, adhering to the specified comparison operator\&. In containers compares the amount of memory assigned to the container instead\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionCPUs=\fR
@@ -1802,6 +2006,8 @@ Verify that the specified number of CPUs is available to the current system\&. T
 "<>"),
 ">=",
 ">"\&. Compares the number of CPUs in the CPU affinity mask configured of the service manager itself with the specified number, adhering to the specified comparison operator\&. On physical systems the number of CPUs in the affinity mask of the service manager usually matches the number of physical CPUs, but in special and virtual environments might differ\&. In particular, in containers the affinity mask usually matches the number of CPUs assigned to the container and not the physically available ones\&.
+.sp
+Added in version 244\&.
 .RE
 .PP
 \fIConditionCPUFeature=\fR
@@ -1864,6 +2070,8 @@ instruction\&. This condition only does something on i386 and x86\-64 processors
 "lahf_lm",
 "abm",
 "constant_tsc"\&.
+.sp
+Added in version 248\&.
 .RE
 .PP
 \fIConditionOSRelease=\fR
@@ -1890,6 +2098,8 @@ and
 (match) and
 "!$="
 (non\-match)\&.
+.sp
+Added in version 249\&.
 .RE
 .PP
 \fIConditionMemoryPressure=\fR, \fIConditionCPUPressure=\fR, \fIConditionIOPressure=\fR
@@ -1907,10 +2117,12 @@ and
 PSI will be checked first, and if not found
 "some"
 will be checked\&. For more details, see the documentation on
-\m[blue]\fBPSI (Pressure Stall Information)\fR\m[]\&\s-2\u[3]\d\s+2\&.
+\m[blue]\fBPSI (Pressure Stall Information)\fR\m[]\&\s-2\u[4]\d\s+2\&.
 .sp
 Optionally, the threshold value can be prefixed with the slice unit under which the pressure will be checked, followed by a
 ":"\&. If the slice unit is not specified, the overall system pressure will be measured, instead of a particular cgroup\*(Aqs\&.
+.sp
+Added in version 250\&.
 .RE
 .PP
 \fIAssertArchitecture=\fR, \fIAssertVirtualization=\fR, \fIAssertHost=\fR, \fIAssertKernelCommandLine=\fR, \fIAssertKernelVersion=\fR, \fIAssertCredential=\fR, \fIAssertEnvironment=\fR, \fIAssertSecurity=\fR, \fIAssertCapability=\fR, \fIAssertACPower=\fR, \fIAssertNeedsUpdate=\fR, \fIAssertFirstBoot=\fR, \fIAssertPathExists=\fR, \fIAssertPathExistsGlob=\fR, \fIAssertPathIsDirectory=\fR, \fIAssertPathIsSymbolicLink=\fR, \fIAssertPathIsMountPoint=\fR, \fIAssertPathIsReadWrite=\fR, \fIAssertPathIsEncrypted=\fR, \fIAssertDirectoryNotEmpty=\fR, \fIAssertFileNotEmpty=\fR, \fIAssertFileIsExecutable=\fR, \fIAssertUser=\fR, \fIAssertGroup=\fR, \fIAssertControlGroupController=\fR, \fIAssertMemory=\fR, \fIAssertCPUs=\fR, \fIAssertCPUFeature=\fR, \fIAssertOSRelease=\fR, \fIAssertMemoryPressure=\fR, \fIAssertCPUPressure=\fR, \fIAssertIOPressure=\fR
@@ -1920,6 +2132,8 @@ Similar to the
 \fIConditionVirtualization=\fR, \&..., condition settings described above, these settings add assertion checks to the start\-up of the unit\&. However, unlike the conditions settings, any assertion setting that is not met results in failure of the start job (which means this is logged loudly)\&. Note that hitting a configured assertion does not cause the unit to enter the
 "failed"
 state (or in fact result in any state change of the unit), it affects only the job queued for it\&. Use assertion expressions for units that cannot operate when specific requirements are not met, and when this is something the administrator or user should look into\&.
+.sp
+Added in version 218\&.
 .RE
 .SH "MAPPING OF UNIT PROPERTIES TO THEIR INVERSES"
 .PP
@@ -1931,7 +2145,7 @@ output\&. In some cases the name of the property is the same as the name of the
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&3.\ \& "Forward" and "reverse" unit properties
+.B Table\ \&4.\ \& "Forward" and "reverse" unit properties
 .TS
 allbox tab(:);
 lB lB lB s.
@@ -2128,6 +2342,8 @@ tool during installation of a unit\&.
 A space\-separated list of additional names this unit shall be installed under\&. The names listed here must have the same suffix (i\&.e\&. type) as the unit filename\&. This option may be specified more than once, in which case all listed names are used\&. At installation time,
 \fBsystemctl enable\fR
 will create symlinks from these names to the unit filename\&. Note that not all unit types support such alias names, and this setting is not supported for them\&. Specifically, mount, slice, swap, and automount units do not support aliasing\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIWantedBy=\fR, \fIRequiredBy=\fR, \fIUpheldBy=\fR
@@ -2171,6 +2387,8 @@ container@\&.target\&.wants/monitor@\&.service
 link to
 monitor@\&.service, which applies to all instances of
 container@\&.target\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIAlso=\fR
@@ -2182,11 +2400,15 @@ and
 will automatically install/uninstall units listed in this option as well\&.
 .sp
 This option may be used more than once, or a space\-separated list of unit names may be given\&.
+.sp
+Added in version 201\&.
 .RE
 .PP
 \fIDefaultInstance=\fR
 .RS 4
 In template unit files, this specifies for which instance the unit shall be enabled if the template is enabled without any explicitly set instance\&. This option has no effect in non\-template unit files\&. The specified string must be usable as instance identifier\&.
+.sp
+Added in version 215\&.
 .RE
 .PP
 The following specifiers are interpreted in the Install section: %a, %b, %B, %g, %G, %H, %i, %j, %l, %m, %n, %N, %o, %p, %u, %U, %v, %w, %W, %%\&. For their meaning see the next section\&.
@@ -2198,7 +2420,7 @@ Many settings resolve specifiers which may be used to write generic unit files r
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&4.\ \&Specifiers available in unit files
+.B Table\ \&5.\ \&Specifiers available in unit files
 .TS
 allbox tab(:);
 lB lB lB.
@@ -2777,11 +2999,16 @@ Interface Portability and Stability Promise
 \%https://systemd.io/PORTABILITY_AND_STABILITY/
 .RE
 .IP " 2." 4
+systemd and Storage Daemons for the Root File System
+.RS 4
+\%https://systemd.io/ROOT_STORAGE_DAEMONS
+.RE
+.IP " 3." 4
 System and Service Credentials
 .RS 4
 \%https://systemd.io/CREDENTIALS
 .RE
-.IP " 3." 4
+.IP " 4." 4
 PSI (Pressure Stall Information)
 .RS 4
 \%https://docs.kernel.org/accounting/psi.html