onitake commented on issue #3613: New rules cause dnsmasq to be restarted instead of reloaded URL: https://github.com/apache/cloudstack/issues/3613#issuecomment-536963236 Restarting should not be necessary for reloading DNS and DHCP records, according to the man page: http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html#lbAG Quote: > When it receives a SIGHUP, dnsmasq clears its cache and then re-loads /etc/hosts and /etc/ethers and any file given by --dhcp-hostsfile, --dhcp-hostsdir, --dhcp-optsfile, --dhcp-optsdir, --addn-hosts or --hostsdir. The dhcp lease change script is called for all existing DHCP leases. If --no-poll is set SIGHUP also re-reads /etc/resolv.conf. SIGHUP does NOT re-read the configuration file. The systemd unit in Debian buster sends a SIGHUP on reload, so it should suffice: ``` ExecReload=/bin/kill -HUP $MAINPID ```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
