From a8c122c4cb6ae0634682663c80f9cace2d1afb50 Mon Sep 17 00:00:00 2001 From: Luca Boccassi Date: Tue, 22 Mar 2022 23:03:23 +0000 Subject: [PATCH] NEWS: adjust MONITOR_ env vars paragraph This actually never shipped in a release, so it's not a backward-incompatible change. Move it down and reword it. --- NEWS | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/NEWS b/NEWS index 625e2cf0e2f..03974aa26d9 100644 --- a/NEWS +++ b/NEWS @@ -23,14 +23,6 @@ CHANGES WITH 251 in spe: and backward compatibility broken instead on the assumption that nobody can be affected given the current state of this interface. - * Service monitor environment variables will only be passed to - OnFailure=/OnSuccess= handlers if exactly one unit lists the handler - unit as OnFailure=/OnSuccess=. In addition, $MONITOR_METADATA is no - longer used, and instead separate variables are set: - $MONITOR_SERVICE_RESULT, $MONITOR_EXIT_CODE, $MONITOR_EXIT_STATUS, - $MONITOR_INVOCATION_ID and $MONITOR_UNIT. For cases when a single - handler needs to watch multiple units, use a templated handler. - * All kernels supported by systemd mix RDRAND (or similar) into the entropy pool at early boot. This means that on those systems, even if /dev/urandom is not yet initialized, it still returns bytes that that @@ -174,6 +166,13 @@ CHANGES WITH 251 in spe: they were installed earlier or later than the appropriate version of the library. + * A new set of service monitor environment variables will be passed to + OnFailure=/OnSuccess= handlers, but only if exactly one unit lists the + handler unit as OnFailure=/OnSuccess=. The variables are: + $MONITOR_SERVICE_RESULT, $MONITOR_EXIT_CODE, $MONITOR_EXIT_STATUS, + $MONITOR_INVOCATION_ID and $MONITOR_UNIT. For cases when a single + handler needs to watch multiple units, use a templated handler. + * A new ExtensionDirectories= setting allows system extensions to be loaded from a directory. (It is similar to ExtensionImages=, but takes a path to a directory, instead of an image.) -- 2.39.2