From 08c1864f0d8714992ffa098f21bb5f763ee3f883 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Thu, 12 Nov 2020 13:05:05 +0100 Subject: meson: allow oomd to be enabled even in release mode A distro (Fedora in particular) may want to enable oomd in a unstable branch for testing, even though the package as a whole is compiled in release mode. Let's emit a warning but otherwise allow this. --- NEWS | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'NEWS') diff --git a/NEWS b/NEWS index 4bda0b2977..468a7a5576 100644 --- a/NEWS +++ b/NEWS @@ -530,13 +530,15 @@ CHANGES WITH 247 in spe: contention for selected parts of the unit hierarchy using the PSI information reported by the kernel, and kills processes when memory or swap pressure is above configured limits. This service is only - enabled in developer mode (see below) and should be considered a - preview in this release. Behaviour details and option names are - subject to change without the usual backwards-compatibility promises. + enabled by default in developer mode (see below) and should be + considered a preview in this release. Behaviour details and option + names are subject to change without the usual backwards-compatibility + promises. * A new helper oomctl has been added to introspect systemd-oomd state. - If also is only available in developer mode and should be considered - a preview without the usual backwards-compatibility promises. + If also is only enabled by default in developer mode and should be + considered a preview without the usual backwards-compatibility + promises. * New meson option -Dcompat-mutable-uid-boundaries= has been added. If enabled, systemd reads the system UID boundaries from /etc/login.defs -- cgit v1.2.1