[Bug 1176710] [NEW] avahi-daemon script holds up run-parts in the if-up.d directory

David Lukacs lukacsd at gmail.com
Mon May 6 02:40:42 UTC 2013


Public bug reported:

Hi,

I hope this is the right forum, or product, to report this issue I found
on a fresh Kubuntu 13.04 install.

I'm using the networkmanager to handle networking, and everything is
running with default settings. I noticed that executing the
/usr/lib/avahi/avahi-daemon-check-dns.sh script takes quite a bit of
time to complete. I have persistent wired network, so the avahi-daemon
script in /etc/network/if-up.d directory tries to execute this when I
start up my computer.

Apart from a prolonged startup time, my real problem was that none of
the scripts, which are alphabetically after avahi-daemon were executed,
because networkmanager has a timeout of some sort on starting up the
network - which eventually always kicked in.

My solution was to simply run the mentioned script in the background, so I modified the avahi-daemon script as follows:
exec /usr/lib/avahi/avahi-daemon-check-dns.sh &

This fixed the problem, but at this stage I'm not sure if I introduced
any other:)

Thank you,
David

** Affects: avahi (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1176710

Title:
  avahi-daemon script holds up run-parts in the if-up.d directory

Status in “avahi” package in Ubuntu:
  New

Bug description:
  Hi,

  I hope this is the right forum, or product, to report this issue I
  found on a fresh Kubuntu 13.04 install.

  I'm using the networkmanager to handle networking, and everything is
  running with default settings. I noticed that executing the
  /usr/lib/avahi/avahi-daemon-check-dns.sh script takes quite a bit of
  time to complete. I have persistent wired network, so the avahi-daemon
  script in /etc/network/if-up.d directory tries to execute this when I
  start up my computer.

  Apart from a prolonged startup time, my real problem was that none of
  the scripts, which are alphabetically after avahi-daemon were
  executed, because networkmanager has a timeout of some sort on
  starting up the network - which eventually always kicked in.

  My solution was to simply run the mentioned script in the background, so I modified the avahi-daemon script as follows:
  exec /usr/lib/avahi/avahi-daemon-check-dns.sh &

  This fixed the problem, but at this stage I'm not sure if I introduced
  any other:)

  Thank you,
  David

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1176710/+subscriptions




More information about the foundations-bugs mailing list