Avahi-daemon-check-dns.sh takes too much time on every connecting to network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
avahi (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Every time I connect to network using NetworkManager, 10s is spent on checking if avahi may be run, which is majority of connecting time.
Control flow is as follows -> NetworkManager -> /sbin/resolvconf -> /etc/resolvconf
If everything is alright (no .local domain, avahi may be run) host shall fail due to timeout, which by default takes 10s.
I believe either dns lookup timeout should be lowered (host -t soa -W 1 .local) or the avahi-daemon-
It is particularly annoying when waking up from suspend - resume takes 3s, main part of network configuration 4s, but then avahi 10s.
To reproduce:
nmcli d disconnect iface <interface>; time nmcli c up id <your network>
chmod -x /usr/lib/
nmcli d disconnect iface <interface>; time nmcli c up id <your network>
Or just:
time /usr/lib/
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: avahi-daemon 0.6.31-2ubuntu4.1
ProcVersionSign
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Sun Nov 24 00:36:05 2013
InstallationDate: Installed on 2013-11-16 (7 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
MarkForUpload: True
SourcePackage: avahi
UpgradeStatus: No upgrade log present (probably fresh install)
The attachment "Proposed fix: lower dns lookup timeout" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]