On Mon, 2021-10-11 at 18:48 +0200, Markus Schönhaber wrote: On a whim, I looked to see what that returns for my system. $ systemctl list-units --state failed UNIT LOAD ACTIVE SUB DESCRIPTION ● network.service loaded failed failed LSB: Bring up/down networking ● rc-local.service loaded failed failed /etc/rc.d/rc.local Compatibility 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. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. Yet, neither of those services has failed. My network is up and running, as normal. And it did execute my rc.local file (though it still lives to run another day, it must be immortal). -- uname -rsvp Linux 3.10.0-1160.42.2.el7.x86_64 #1 SMP Tue Sep 7 14:49:57 UTC 2021 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.

On Tue, 2021-10-12 at 08:36 +0200, Markus Schönhaber wrote: Nothing really jumps out at me, I'll have a look the next time I reboot. One thing that comes to mind, though; is that query (systemctl list- units --state failed) a command that shows current failure status, or will it still list things as failed if they failed at one stage, even if they succeeded later on? -- uname -rsvp Linux 3.10.0-1160.42.2.el7.x86_64 #1 SMP Tue Sep 7 14:49:57 UTC 2021 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.

On 10/12/21 02:03, Tim via users wrote: That worked anD showed that a line in fstab was in error mounting a directory on my NAS. Hadn't tried to access that particular directory.