@Trent: I really don't have any context from the original rationale left. So in the absence of better data, we should indeed follow Debian -- if there are no major bug reports about that, this can't be completely broken. Does Debian do the [NOTFOUND=RETURN] thing? I suppose not?
Please do grab the bug if you have some time to investigate/handle this, I'm afraid I'm swamped. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1441008 Title: under systemd avahi-daemon doesn't stay disabled when .local is detected Status in avahi package in Ubuntu: Triaged Bug description: When avahi daemon detects .local unicast domain, the daemon is disabled. When a user tries to resolve a domain name through nss, the daemon starts up. The root cause is most likely in systemd that starts the daemon when an application tries to access the socket through the systemd managed socket file. This behavior wasn't observed in 14.10 or earlier releases, thus the assumption towards systemd socket activation. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: avahi-daemon 0.6.31-4ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 7 09:51:43 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-16 (506 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: avahi UpgradeStatus: Upgraded to vivid on 2015-03-18 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1441008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
