Improve dropbear.service to avoid failed state after stop (#1286)

So far the exit code has been evaluated, which seems to be non-zero even
with a regular term signal. With that systemd assumed the service is in
a failed state, when in fact this seems the regular behavior of dropbear
when shutting it down.
This commit is contained in:
Stefan Agner 2021-03-24 19:13:43 +01:00 committed by GitHub
parent fdd8c246dd
commit ab19c8c6cf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -3,6 +3,9 @@ RequiresMountsFor=/etc/dropbear
ConditionFileNotEmpty=/root/.ssh/authorized_keys
[Service]
Type=forking
PIDFile=/run/dropbear.pid
ExecStartPre=
ExecStart=
ExecStart=/usr/sbin/dropbear -F -R -E -p 22222 -s
ExecStart=-/usr/sbin/dropbear -R -E -p 22222 -s
KillMode=mixed