> Sent: Tuesday, December 24, 2024 at 7:39 AM
> From: "Oliver Schode" <oliver.sch...@online.de>
> To: debian-user@lists.debian.org
> Subject: Re: Systemctl masked/disabled/etc
>
> Hi,
>
> looks like I'm the only one yet as I take it, he wasn't asking about
> meanings of, or differences between states but rather worries about
> defaults he may have inadvertently changed. This is about what is
> essential or required for system operation.
>
> > Is there any point to worrying about what's masked and disabled if I
> > don't have a specific technical reason?
>
> I don't think so, or at least I never had to think about it in all
> those years with systemd. Anything essential or important that's
> missing or failing you'd notice before long, but then you'll have your
> technical reason. Of course, if you've touched your system to the point
> where you're unsure how to get back, it's easy enough to
> reset/reinstall affected packages but usually than shouldn't be
> necessary.
>
> > 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 "normal" system obviously can look all kinds of things. Maybe you
> really meant vanilla or out-of-the-box and as far as I'm concerned when
> it comes to masking it doesn't look much different from what I have
> now. And either of,
>
> `systemctl list-units --state=masked` (to see what's loaded+masked)
> or
> `systemctl lits-unit-files --state=masked` (everything installed+masked)
>
> wouldn't print an overly long list. And those (few) I masked myself
> only show for loaded. You can naturally try this with state=disabled as
> well, in that case it's slightly more interesting to compare current
> and preset values.
>
>
Masked units don't hurt a thing, that is if you known what your doing and know
why you want or need to mask certain units.
Now under debian I remove the services/packages, for example I remove
everything/all "debian networking" and then setup networking in a sane and
workable way. The "debian way" will just cause all kind of grief, which is not
necessary and that is why I remove it.
systemctl list-units --state=masked
UNIT LOAD ACTIVE SUB DESCRIPTION
● rpcbind.service masked inactive dead rpcbind.service
● rpcbind.socket masked inactive dead rpcbind.socket
Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of
SUB.
SUB → The low-level unit activation state, values depend on unit
type.
2 loaded units listed.
[alarm@alarm ~]$
I am using NFS and don't want or need NFS V3 as I only wand NFS V4.
[alarm@alarm ~]$ sudo exportfs
/srv 192.168.50.0/24
