** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441008
Title:
under systemd avahi-daemon doesn't stay disabled when
Sorry, I keep having no time for this, please grab.
** Changed in: avahi (Ubuntu)
Milestone: ubuntu-16.02 => None
** Changed in: avahi (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
@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
The 3rd level is a good indicator that we really want a proper DNS name.
I did investigate this very briefly back when this problem first
occurred.
I also think that the nsswitch alteration is a good solution in the
short term. The issue on the long term is that people with .local domain
will see
I was re-visiting this recently, I'm fairly sure we can get rid of this
requirement to stop avahi with a .local by reconfiguring nsswitch.conf
to remove the [NOTFOUND=RETURN].
Do you know where the initial discussion determining why to do this was
had?
My general understanding is that because of
** Changed in: avahi (Ubuntu)
Milestone: ubuntu-16.01 => ubuntu-16.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441008
Title:
under systemd avahi-daemon doesn't stay disabled when .local is
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: avahi (Ubuntu)
Milestone: None => ubuntu-16.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441008
Indeed, this should be fixed in /usr/lib/avahi/avahi-daemon-check-dns.sh
. When running under systemd ([ -d /run/systemd/system ]) then the
.socket needs to be stopped too, not just the .service.
** Changed in: avahi (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notificat
** Summary changed:
- avahi-daemon doesn't stay disabled when .local is detected
+ under systemd avahi-daemon doesn't stay disabled when .local is detected
** Tags added: rls-w-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
