Avahi daemon should not try to resolve hostnames during bootup
Bug #80268 reported by
Mephisto
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| avahi (Ubuntu) |
Fix Released
|
Undecided
|
Scott James Remnant (Canonical) | ||
Bug Description
Today i took some time to figure out why my bootup process seems to hang for over 10 seconds, and it seems to be caused by the avahi-daemon. Bootchart shows avahi running a 'host' process, so it's probably caused by the lack of a network connection, making the resolve attempt time out.
I don't have a network connection during bootup. I'm using NetworkManager on a laptop with wifi, so my connection is not available until nm-applet connects it (after logging in).
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #1 |
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #2 |
| Changed in avahi: | |
| assignee: | nobody → keybuk |
| status: | Unconfirmed → Fix Released |
To post a comment you must log in.
Add
[ "$IFACE" != "lo" ] || exit 0
to the top of the script...
Even if you have a unicast .local domain resolvable on just your loopback device, I suspect you won't care until a real network device is brought up.