Hi Sjoerd,
Excerpts from Sjoerd Simons's message of 2011-09-03 14:53:27 +0200:
> Sure attached. Looks like you're using a dbus service, while by default
> (afaik) dnsmasq isn't configured to connect to dbus, so it'll just wait
> forever and ever..
Ah, yes, indeed. Sorry, I completely missed that this is not the default in the
dnsmasq config :). DBus activation makes sense because it’s the best way for
systemd to know when the service has actually started.
I will update the service file with all the points we have discussed in this
bug report soon. In the meantime, can you please try using the following line?
ExecStart=/usr/sbin/dnsmasq -k --enable-dbus
That should make it start correctly.
> As long as you ensure NM still correctly interacts with dnsmasq such
> that all local nameserver queries can go via dnsmasq and dnsmasq uses
> the resolv.conf file written by NM this might be true.
NetworkManager can use dnsmasq for this purpose, just put "dns=dnsmasq" in the
[main] section of /etc/NetworkManager/NetworkManager.conf
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
