Comment 78 for bug 959037

> NM kills and starts a new dnsmasq process every time this file changes. Will that be a problem for your LTSP setup where dnsmasq is also the DHCP server?

The most time consuming operation that dnsmasq does in our setups is sending the kernel/initrd via TFTP. That takes a few seconds. If the teacher activated a VPN connection at that time and dnsmasq was killed+respawned, the client wouldn't boot. But I think that problem would be too rare, so it sounds acceptable.

I don't quite understand why dnsmasq needs to be restarted though. /var/run/nm-dns-dnsmasq.conf only contains the nameservers, and dnsmasq supports polling a resolv.conf for changes. Can't that be used instead to completely avoid restarting dnsmasq? (it wouldn't even need a SIGHUP in that case...)