From f8f2b23fb7e902831befd7b72613a82fe627b085 Mon Sep 17 00:00:00 2001 From: Colin Guthrie Date: Sun, 29 Apr 2012 11:52:09 +0000 Subject: services: Use no-block mode for service start/stop under systemd. This is perhaps the same issue as the 'cpufreq' bug on first boot, but by changing things to use systemctl directly, I have inadvertantly bypased the solution and reintroduced the bug. As there is likely no reason to block, we will simply use no-block mode unconditionally. Longer term, we may need to decide under what context we are restarting/starting a given service (i.e. in an interactive GUI vs from a script) and use the appropriate mode with appropriate user feedback. https://bugs.mageia.org/show_bug.cgi?id=4439 --- perl-install/services.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'perl-install/services.pm') diff --git a/perl-install/services.pm b/perl-install/services.pm index 99172f78e..6eab201be 100644 --- a/perl-install/services.pm +++ b/perl-install/services.pm @@ -326,7 +326,7 @@ sub _set_service { sub _run_action { my ($service, $action) = @_; if (running_systemd()) { - run_program::rooted($::prefix, '/bin/systemctl', $action, "$service.service"); + run_program::rooted($::prefix, '/bin/systemctl', '--no-block', $action, "$service.service"); } else { run_program::rooted($::prefix, "/etc/rc.d/init.d/$service", $action); } -- cgit v1.2.1