Two additional commands I regularly use as a Sysadmin are
systemctl status without any unit to list show the general system status (lists units that are running, units that are starting and failed units right at the top)
And then
systemctl list-units --failed
To show me just the failed units and did deeper what the problem is.
On a properly set up system I should quickly be able to ascertain if everything is “up and running” just by systemds status
Two additional commands I regularly use as a Sysadmin are
systemctl statuswithout any unit to list show the general system status (lists units that are running, units that are starting and failed units right at the top) And thensystemctl list-units --failedTo show me just the failed units and did deeper what the problem is.On a properly set up system I should quickly be able to ascertain if everything is “up and running” just by systemds status
You can also use
systemctl status $pidto find out what service a process is from.You can … WHAT!?
Wow I did not know that. Incredibly helpful
Oooh. Thank you, I didn’t know that.
This and
systemctl cat $unitare my favorites.Didn’t know that. Thanks!
You can skip
list-unitsand just dosystemctl --failedYou can even drop the
list-unitsand just usesystemctl --failed