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 103f841a5768267b4c80b1e4f7b84e3974dca135..5cd068ad2468f9b8fe639155a350d7ab75da9208 100755 (executable)
--- 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