12.10.21, 08:03 +0200, Tim via users:
$ 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).
Well, if systemctl reports them as failed, there's probably a reason to
do so. My guess would be, both scripts (as "LSB:" indicates,
network.service is just a generated systemd-wrapper around the old SysV
init script) returned a non-zero exit code. There might be some hint in
the logs why they did that.
--
Regards
mks
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
