Package: unbound Version: 1.6.4-1 When unbound is stopped, its PID file is left behind causing subsequent service starts to complain like that:
unbound[178]: [178:0] warning: did not exit gracefully last time (124) Please find a patch that tells systemd where the PID is so that it can delete it once unbound is stopped. Regards, Simon
commit ebd7d61e0c79dbd85c99c878d06aff7fc09b919c
Author: Simon Deziel <si...@sdeziel.info>
Date: Tue Jul 4 15:47:00 2017 +0000
systemd: let systemd know about the pid file
This let systemd delete it when the service is stopped and avoids
getting "warning: did not exit gracefully last time ($OLDPID)" on
subsequent service start.
diff --git a/debian/unbound.service b/debian/unbound.service
index e20aa56..6d3bf93 100644
--- a/debian/unbound.service
+++ b/debian/unbound.service
@@ -14,6 +14,7 @@ ExecStartPre=-/usr/lib/unbound/package-helper root_trust_anchor_update
ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS
ExecStopPost=-/usr/lib/unbound/package-helper chroot_teardown
ExecReload=/usr/sbin/unbound-control reload
+PIDFile=/run/unbound.pid
[Install]
WantedBy=multi-user.target
signature.asc
Description: OpenPGP digital signature
