From: Maryse47 <41080948+Maryse47@users.noreply.github.com>
Date: Fri, 20 Sep 2019 10:07:37 +0000 (+0000)
Subject: unbound.service.in: do not fork into the background
X-Git-Tag: release-1.9.6rc1~100^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F83%2Fhead;p=thirdparty%2Funbound.git

unbound.service.in: do not fork into the background

This is needed when unbound config doesn't set "do-daemonize: no" by itself otherwise starting service fails with:
 systemd[1]: unbound.service: Got notification message from PID <PID>, but reception only permitted for main PID which is currently not known

https://github.com/NLnetLabs/unbound/blob/release-1.9.3/doc/example.conf.in#L236
---

diff --git a/contrib/unbound.service.in b/contrib/unbound.service.in
index c5f95c76c..6726f9d8c 100644
--- a/contrib/unbound.service.in
+++ b/contrib/unbound.service.in
@@ -10,7 +10,7 @@ WantedBy=multi-user.target
 
 [Service]
 ExecReload=/bin/kill -HUP $MAINPID
-ExecStart=@UNBOUND_SBIN_DIR@/unbound
+ExecStart=@UNBOUND_SBIN_DIR@/unbound -d
 NotifyAccess=main
 Type=notify
 CapabilityBoundingSet=CAP_IPC_LOCK CAP_NET_BIND_SERVICE CAP_SETGID CAP_SETUID CAP_SYS_CHROOT CAP_SYS_RESOURCE CAP_NET_RAW