units: don't block on terminating agents

Terminating the plymouth/console agents when the wall agent takes over
can happen asynchronously, after all the pw queries are async anyway and
hence can be seen by both the plymouth/console agents and the wall
agent.

By stopping the two agents with "--no-block" we add a bit of robustness,
since trouble of them exiting won't block the wall agent to start.

This addresses the issue the previous commit fixes in a different way.

diff --git a/units/systemd-ask-password-wall.service b/units/systemd-ask-password-wall.service
index c785614e1e3071887f6887f1b9690e7863c74248..20890d08c2e7920e4a36d2de9c5cd83d16c1624f 100644 (file)
--- a/units/systemd-ask-password-wall.service
+++ b/units/systemd-ask-password-wall.service
@@ -13,7 +13,7 @@ Documentation=man:systemd-ask-password-wall.service(8)
 After=systemd-user-sessions.service
 
 [Service]
-ExecStartPre=-systemctl stop systemd-ask-password-console.path systemd-ask-password-console.service systemd-ask-password-plymouth.path systemd-ask-password-plymouth.service
+ExecStartPre=-systemctl stop --no-block systemd-ask-password-console.path systemd-ask-password-console.service systemd-ask-password-plymouth.path systemd-ask-password-plymouth.service
 ExecStart=systemd-tty-ask-password-agent --wall
 Type=notify
 SystemCallArchitectures=native