Re: Systemctl masked/disabled/etc

To: debian-user@lists.debian.org
Subject: Re: Systemctl masked/disabled/etc
From: Greg Wooledge <greg@wooledge.org>
Date: Sun, 22 Dec 2024 08:35:30 -0500
Message-id: <[🔎] 20241222133530.GQ29532@wooledge.org>
Mail-followup-to: debian-user@lists.debian.org
In-reply-to: <[🔎] 74578029-5a49-40d3-9352-0238bcd2373b@app.fastmail.com>
References: <[🔎] 74578029-5a49-40d3-9352-0238bcd2373b@app.fastmail.com>

On Sun, Dec 22, 2024 at 01:16:31 -0500, Alex Wahl wrote:
> Is there any point to worrying about what's masked and disabled if I don't have a specific technical reason? The reason I asked it really just because I'm wondering if I accidentally set a unit to that in the past I shouldn't have; I don't really know what a "normal" system looks like

A service that's masked can NEVER be activated, by anything, unless
it's unmasked first.

A service that's disabled won't be started automatically, but it
could be activated by a different service.  Or started manually.

Reply to:

Follow-Ups:
- Re: Systemctl masked/disabled/etc
  - From: Max Nikulin <manikulin@gmail.com>

References:
- Systemctl masked/disabled/etc
  - From: "Alex Wahl" <awahl1138@fastmail.com>

Prev by Date: Re: Finding suitable icons displayable on MATE's panel
Next by Date: Re: Finding suitable icons displayable on MATE's panel
Previous by thread: Re: Systemctl masked/disabled/etc
Next by thread: Re: Systemctl masked/disabled/etc
Index(es):
- Date
- Thread