On Sun 10 Apr 2022 at 08:10:17 -0400, gene heskett wrote: > On Sunday, 10 April 2022 07:17:42 EDT The Wanderer wrote: > > On 2022-04-10 at 07:08, gene heskett wrote: > > > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote: > > >> I just don't install it. > > > > > > And how do you accomplish that? Its automatically installed AFAIK. > > > And once installed, apt will not remove it without destroying the > > > install. rm or chmod -x seems to be the only way, and nothing > > > complains. > > > > What package(s), by exact name, are you referring to? That is, which > > package(s) is it that produce this effect when you try to remove them? > > > > On my computer, I have several libavahi* packages, which could not be > > removed without removing large swaths of packages - but I also have > > avahi-daemon and avahi-utils, which can be removed with few if any side > > effects (as far as triggering removal of other packages goes). > > > > And since the subject at hand in this branch of the thread appears to > > be avahi-daemon, surely removing that single package should be enough > > to prevent avahi from doing anything undesirable? > > Which IMO It should be but apt will not remove avahi-daemon on any of my > buster machines or on bullseye without taking "large swaths" of stuff > with it. > > Tomas just found, and I have now edited /etc/default/avahi-daemon to > officialy shut it off, ditto for brytty, leaving a killed orca spewing 20
I do not think AVAHI_DAEMON_DETECT_LOCAL does what you think it does. It applies to detection of *unicast* dns servers. -- Brian.
