[SOLVED] avahi-daemon disabled but is still started

notadoc · 05-06-2021, 02:22 PM

I've run systemctl to disable avahi-daemon.service and avahi-daemon.socket. And yet, they both are running! I suspect that cupsd is responsible, but I don't know how to prove it:

Quote:

● avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket
Loaded: loaded (/lib/systemd/system/avahi-daemon.socket; disabled; vendor preset: enabled)
Active: active (running) since Thu 2021-05-06 13:18:56 EDT; 5min ago
Triggers: ● avahi-daemon.service

● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/lib/systemd/system/avahi-daemon.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2021-05-06 13:18:57 EDT; 2min 44s ago
TriggeredBy: ● avahi-daemon.socket

What can I do to prevent these progs from running. I need cupsd for printing.

berndbausch · 05-06-2021, 03:28 PM

Disabling a unit does not stop it. It only prevents it from starting automatically, e.g. when rebooting. To stop it, use systemctl stop avahi-daemon or systemctl disable avahi-daemon --now.

notadoc · 05-07-2021, 12:39 PM

I'm aware of the

Code:

systemctl stop

option, but I want to *prevent* the daemon/socket startup, instead of using

Code:

systemctl stop

at each boot. Perhaps

Code:

systemctl mask

is the way to go?

berndbausch · 05-07-2021, 06:42 PM

When you disable a unit, it won't be activated automatically. It can still be activated manually with systemctl start.
When you mask a unit, it can't be activated at all.

You say that you want to prevent Avahi startup. If you mean automatic startup, you should be OK, because you disabled both units. If you want to prevent manual startup, mask them.

notadoc · 05-08-2021, 02:01 PM

Looks like 'mask' is the solution to my problem. I just wish I knew which app was calling avahi-daemon.socket.
Thanks for replying.