[knot-dns-users] Re: systemd notify

On 08/10/2026 13:51, Daniel Salzman via knot-dns-users wrote: Hi Daniel, Yes, our build of Knot DNS 3.5.8 has systemd integration: # knotd -VV | grep -i systemd Systemd integration: yes D-Bus support: systemd The unit file looks like this: # systemctl cat knot # /usr/lib/systemd/system/knot.service [Unit] Description=Knot DNS Server After=network-online.target [Service] LimitNOFILE=1048576 ExecStart=/usr/sbin/knotd ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target # /etc/systemd/system/knot.service.d/override.conf [Service] Type=notify-reload ExecReload= Notice that in the override, I have set the "Type" to "notify-reload" and reset the reload command to empty, because "notify-reload" implies that systemd will send a HUP signal to the process when I request a reload, so there is no need for an ExecReload command. However, as I showed in my previous message, the "systemctl reload" command hangs, and then after 90 seconds, systemd times out and aborts the reload, and emits an error message. So somehow systemd is not seeing the "READY=1" message. This is the puzzling bit. There must be something subtle I'm missing. Regards, Anand