Run unbound-checkconf after unbound-anchor

Otherwise unbound.service won't start when the auto-trust-anchor file
(which would be created by unbound-anchor) is missing.

diff --git a/unbound.service b/unbound.service
index b6316100064110d479aa32890f8ba6e6a49a3c2e..87bc9d8d44cc6357809c490d0c1c3583ec196799 100644 (file)
--- a/unbound.service
+++ b/unbound.service
@@ -6,8 +6,8 @@ After=network.target
 
 [Service]
 Type=forking
 
 [Service]
 Type=forking

-ExecStartPre=/usr/sbin/unbound-checkconf /etc/unbound/unbound.conf

 ExecStartPre=-/usr/sbin/unbound-anchor -v -a /var/lib/unbound/root.key
 ExecStartPre=-/usr/sbin/unbound-anchor -v -a /var/lib/unbound/root.key

+ExecStartPre=/usr/sbin/unbound-checkconf /etc/unbound/unbound.conf

 ExecStart=/usr/sbin/unbound -c /etc/unbound/unbound.conf
 ExecReload=/usr/sbin/unbound-checkconf /etc/unbound/unbound.conf
 ExecReload=/bin/kill -HUP $MAINPID
 ExecStart=/usr/sbin/unbound -c /etc/unbound/unbound.conf
 ExecReload=/usr/sbin/unbound-checkconf /etc/unbound/unbound.conf
 ExecReload=/bin/kill -HUP $MAINPID