[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting

[Alkis Georgopoulos]

> 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...)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/959037

Title:
  NM-controlled dnsmasq prevents other DNS servers from starting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions