Howdy,
Instead, consider:
1. The only reason this script needs to run when an interface is taken
down is to restart avahi if avahi was disabled due to .local in the dns
when the the interface was brought up.
2. If that's the case, then /var/run/avahi-daemon/disabled-for-unicast-local
should already exist, created by this script when the interface came
up.
3. So if it doesn't exist, the script doesn't need to do anything else
when the interface is taken down. Just test for the file and exit if
it's not there.
This assumes you are only ever connected to one network and downing one
interface won't change the unicast .local situation, which is not correct.
Having said that, this delay is also annoying.
I wonder if we can background this check without causing hassles?
Cheers,
Trent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]