On Fri 27 Dec 2024 at 11:27:18 (-0500), eben wrote: > On 12/27/24 11:18, David Wright wrote: > > 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. > > Hmm. Maybe that applies to certain versions? I don't think I've touched > that directory.
Sorry, but did you only read the first two lines of my post? You snipped all the examples I gave and their explanations, viz: $ ls -AlFR /etc/systemd/ | grep 'null' [ … … ] $ ls -AlFR /etc/systemd/ | grep '^\-' [ … … ] $ systemctl list-unit-files --state=disabled [ … … ] $ systemctl status whatever.service/timer/socket/whichever [ … … ] Those listings will include everything underneath, corresponding with the trees in /lib/systemd/, /run/systemd/, /usr/local/lib/systemd/, and so on. > []~$ ls -l /etc/systemd/ > total 44K > 4.0K -rw-r--r-- 1 root root 1.3K Sep 20 2023 journald.conf > 4.0K -rw-r--r-- 1 root root 1.6K Sep 20 2023 logind.conf > 4.0K -rw-r--r-- 1 root root 846 Sep 20 2023 networkd.conf > 4.0K -rw-r--r-- 1 root root 670 Sep 20 2023 pstore.conf > 4.0K -rw-r--r-- 1 root root 953 Sep 20 2023 sleep.conf > 4.0K -rw-r--r-- 1 root root 2.1K Sep 20 2023 system.conf > 4.0K -rw-r--r-- 1 root root 864 Sep 20 2023 timesyncd.conf > 4.0K -rw-r--r-- 1 root root 1.4K Sep 20 2023 user.conf Yes, those are the ones I mentioned: “systemd-owned .conf files (typically listed first) that show the default values for parameters, that is if you haven't modified them”, which you appear not to have done. BTW is your ls command aliased? Cheers, David.
