From ab19c8c6cf82452781eaded11b8e71cf817b06d3 Mon Sep 17 00:00:00 2001 From: Stefan Agner Date: Wed, 24 Mar 2021 19:13:43 +0100 Subject: [PATCH] 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. --- .../etc/systemd/system/dropbear.service.d/hassos.conf | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/buildroot-external/rootfs-overlay/etc/systemd/system/dropbear.service.d/hassos.conf b/buildroot-external/rootfs-overlay/etc/systemd/system/dropbear.service.d/hassos.conf index 5da76e50a..1719de873 100644 --- a/buildroot-external/rootfs-overlay/etc/systemd/system/dropbear.service.d/hassos.conf +++ b/buildroot-external/rootfs-overlay/etc/systemd/system/dropbear.service.d/hassos.conf @@ -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