On 25/02/11 19:29, Michael Biebl wrote:
Am 25.02.2011 18:58, schrieb Simon Kelley:
On 25/02/11 16:55, Michael Biebl wrote:
Thanks Jérémy for the followup.
Am 25.02.2011 17:32, schrieb Jérémy Lal:
this bug comes from dnsmasq update to 2.57-1
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/725041
Simon, I'd like your input on this as dnsmasq maintainer, how this
should be fixed.
Thanks,
Michael
It looks like the bug may be longstanding,
dnsmasq --conf-file filename
will not read filename, it will read nothing. (It sets the conf-file to
be empty, and the filename argument is superfluous) All that's changed
in 2.57 is that dnsmasq sanity-checks better.
The correct command line is either
dnsmasq --conf-file=filename
or
dnsmasq -C filename
Looking at the source code for NetworkManager, the latter makes for an
easier patch.
While looking at the code in NetworkManager [1], I have to note that
generating a random, non-existent junk file to circumvent dnsmasq looks
rather ugly to me.
If we already have to use this trick, couldn't we at least use something
like --conf-file=/dev/null or would this not have the desired effect.
Is there maybe a nicer way to tell dnsmasq to *not* read the global
configuration file?
Ah, I hadn't read up in the source code to that part.
It's completely unnecessary:
dnsmasq --conf-file
suppresses reading the default configuration file. Just stop adding the
junk filename (which never did anything, anyway) and dnsmasq will no
longer complain.
Simon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
