On Sun 22 Dec 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
Typically, a vanilla system will have very few files in /etc/systemd/ that aren't just symlinks to files in /lib/systemd or /usr/lib/systemd. $ ls -AlFR /etc/systemd/ | grep 'null' will search for things that are masked, and the timestamp will tell you when the change was made. (Some could date back to installation.) $ ls -AlFR /etc/systemd/ | grep '^\-' will search for ordinary files that you might have written yourself to override systemd's default behaviour. However, there are some systemd-owned .conf files (typically listed first) that show the default values for parameters, that is if you haven't modified them. Again, the timestamps may jog your memory. $ systemctl list-unit-files --state=disabled Because disabling services removes files, you may need this command to give you an overview of disabled services etc. But there could be many that normally show as such, so you'll need to check with: $ systemctl status whatever.service/timer/socket/whichever Cheers, David.
