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.This and
systemctl cat $unitare my favorites.You can … WHAT!?
Wow I did not know that. Incredibly helpful
Oooh. Thank you, I didn’t know that.
Didn’t know that. Thanks!
You can even drop the
list-unitsand just usesystemctl --failedYou can skip
list-unitsand just dosystemctl --failed
This is somewhat related to the article but also a little off topic.
I started using Linux about 6 months ago now and I feel like it’s been a continual learning experience (in a positive way). I was comfortable enough with Windows that I was on autopilot with most things.
I’ve used systemctl previously but I love seeing articles like this, so freely available, where I have the chance to learn a lot more about my system.
Tangent over, just had this on my mind for a while and needed to share.
Here’s some more examples:
Systemctl edit: create an extension for the unit file and add some changes
S edit --full: edit the full unit file (and timer too iirc)
S enable --now:enable + start
S disable --now: disable + stopSide note: does anyone enable or use the magic sysreq key anymore?
I do, and used it today as well. My AMD gpu sometimes when booting fails to set the correct resolution on the 3rd display, and that causes the graphical session to freeze for some reason and I have to force a restart with sysreq and start the graphical session with a weird script that sets a custom res lol.
I use it for fun
And sometimes for testing system survivability
Gotta keep that kernel on its toes.
If you have a system with long-running leaky browser instances, Alt-SysRq-F is a lifesaver. It calls oom_kill, sacrificing one process to save the rest.
It may actually be a security hazard since there is a small chance of e.g. OOM killing your lock screen or other such process.
Please tell me that needs physical access to work. Now that I think about it - how does sysrq even work with laptop keyboards?
Not on Wayland
Is there an equivalent in SysVInit?
There always is. Usually easier.
PCLinuxOS, an offshoot of Mandriva (itself the child of the Mandrake/Conectiva union, both a long derivative of RedHat), still avoids systemd to provide a distro with massive versatility and fast boots.
