Re: bug report (and fix) network up/down delayed 10 seconds
Dear Klaus,
> What about changing AVAHI_DAEMON_DETECT_LOCAL=1 to
> AVAHI_DAEMON_DETECT_LOCAL=0 in
> /etc/default/avahi-daemon?
>
> Or, maybe just removing /etc/network/if-up.d/avahi-daemon and
> /etc/network/if-post-down.d/avahi-daemon until it is fixed upstream?
>
In both cases, that would also prevent avahi from detecting the "local"
domain when a nameserver is configured, allowing the avahi daemon to be
run when it should not. For someone wishing to use avahi, this may result
in contention problems that are much more difficult to diagnose than the
present problem.
I think the ideal interim solution is to patch the script with the
troublesome greps. For me, it makes sense to put my local fix in
resolv.conf: I'm not interested in avahi at the moment, but I am running
named on one of my machines (the starting point for the configuration came
from a script of substantial pedagogical value called
"knoppix-terminalserver"), so /etc/resolv.conf is something I pay much
more attention to.
By the way, not to mingle topics in one post, but...
Mentioning knoppix-terminalserver reminds me: The named.conf option
"query-source address * port 53;" results in the following log message:
/etc/bind/named.conf.options:2: using specific query-source port
suppresses port randomization and can be insecure.
I don't like my programs feeling insecure, and I found no ill-effects from
removing this option. Is there some reason I might want to keep that
option, or is it just for debugging?
Do you have any thoughts on the change I proposed for knoppix-halt to
solve the wake-on-lan problem?
Thanks again for a wonderful tool!
Kind regards,
Andrew
Reply to: