From 341ee9fe5e9810a8cc1a7d7156da0158f78dce68 Mon Sep 17 00:00:00 2001 From: Colin Guthrie Date: Tue, 14 Jan 2014 13:50:23 +0000 Subject: services.pm: Use no-reload mode when interacting with systemd. Basically, there seems to be an issue right now if we do lots of reloads. It seems to be somewhat racy and systemd gets generally confused when we do this during boot (which we do) and trigger a reload. The reload isn't strictly needed, as we do also explicitly start the services we enable (with --no-block so that we don't cause a deadlock) so all *should* be 99% OK. Using it at runtime might mean we don't have fully up-to-date enablement status, but being able to boot wins at the moment. --- perl-install/install/NEWS | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'perl-install/install') diff --git a/perl-install/install/NEWS b/perl-install/install/NEWS index 8956b2d8e..b38f65857 100644 --- a/perl-install/install/NEWS +++ b/perl-install/install/NEWS @@ -1,3 +1,7 @@ +- services: + o use --no-block with chkconfig and systemctl enable to prevent systemd reload + and potential crash (especially during first/live boot) + Version 16.21 - 13 January 2014 - partitioning: -- cgit v1.2.1