bbc56d0b27
Once ntpdate.service is fixed to order itself After nss-lookup.target, there will be an ordering loop. To reproduce this do: [root@notas ~]# yum -y install unbound ntpdate chrony [root@notas ~]# systemctl enable ntpdate.service chronyd.service unbound-anchor.timer unbound.service unbound-anchor.service [root@notas ~]# systemd-analyze verify /usr/lib/systemd/system/* And then in the output you can find: Found ordering cycle on ntpdate.service/stop Found dependency on nss-lookup.target/start Found dependency on unbound.service/start Found dependency on unbound-anchor.service/start Found dependency on unbound-anchor.timer/start Found dependency on time-sync.target/start Found dependency on chrony-wait.service/stop Found dependency on chronyd.service/stop Found dependency on ntpdate.service/stop Signed-off-by: Tomas Hozza <thozza@redhat.com>
20 lines
545 B
Desktop File
20 lines
545 B
Desktop File
[Unit]
|
|
Description=Unbound recursive Domain Name Server
|
|
After=network.target
|
|
After=unbound-keygen.service
|
|
Wants=unbound-keygen.service
|
|
Wants=unbound-anchor.timer
|
|
Before=nss-lookup.target
|
|
Wants=nss-lookup.target
|
|
|
|
[Service]
|
|
Type=simple
|
|
EnvironmentFile=-/etc/sysconfig/unbound
|
|
ExecStartPre=/usr/sbin/unbound-checkconf
|
|
ExecStartPre=-/usr/sbin/unbound-anchor -a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem
|
|
ExecStart=/usr/sbin/unbound -d $UNBOUND_OPTIONS
|
|
ExecReload=/usr/sbin/unbound-control reload
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|