A short term documentation only fix would be to describe the behavior of `DNSMASQ_EXCEPT` (in relation to resolvconf) in `/etc/default/dnsmasq` so that users don't have to RTFS of `/etc/init/dnsmasq` to figure out how to do this...
The changelog comment calling `DNSMASQ_EXCEPT` "obsolete" is wrong, since it is the only way to keep this package from adding `127.0.0.1` to resolvconf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1042275 Title: Please enhance dnsmasq to talk directly to resolvconf and to register only its actual listening address(es) Status in dnsmasq package in Ubuntu: Triaged Bug description: The standalone Dnsmasq (from the dnsmasq package) is preventing the NetworkManager-controlled dnsmasq from starting. By setting ENABLED=0 in /etc/default/dnsmasq instead of ENABLED=1, name service started working again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2 Uname: Linux 3.5.0-12-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Mon Aug 27 10:48:06 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2012-08-27T10:43:43.717591 mtime.conffile..etc.dnsmasq.conf: 2012-05-26T23:51:39.391123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1042275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
