From: Alan Jenkins Date: Wed, 30 Aug 2017 16:11:31 +0000 (+0100) Subject: sulogin-shell: remove ineffective job mode option from `systemctl isolate` (#6627) X-Git-Tag: v235~203 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3f1a3d4ac57867dc9ac0e98028c4b6f0fa93ad60;p=thirdparty%2Fsystemd.git sulogin-shell: remove ineffective job mode option from `systemctl isolate` (#6627) `systemctl default` uses job mode `isolate` (see `action_table`). The job mode option is ignored. Note that exiting the emergency shell service by using e.g. `systemctl isolate multi-user` or `systemctl start multi-user.target` already kills `emergency.service`. There's only a potential conflict between your command and the command in systemd-sulogin-shell if you run something like `systemctl start --no-block multi-user.target; exit`. Which is nothing like what we told them to do :). --- diff --git a/src/sulogin-shell/systemd-sulogin-shell.in b/src/sulogin-shell/systemd-sulogin-shell.in index 103f841a576..5cd068ad246 100755 --- a/src/sulogin-shell/systemd-sulogin-shell.in +++ b/src/sulogin-shell/systemd-sulogin-shell.in @@ -9,4 +9,4 @@ echo "system logs, \"systemctl reboot\" to reboot, \"systemctl default\" or ^D t echo "into default mode." @SULOGIN@ -@SYSTEMCTL@ --job-mode=fail --no-block default +@SYSTEMCTL@ --no-block default