Reply to post: @jerky_rs read the documentation

Linux greybeards release beta of systemd-free Debian fork


@jerky_rs read the documentation

systemctl status --state active

systemctl list-sockets

systemctl list-dependencies ssh.service {--before | --after}

journalctl -u ssh.service

systemd-analyze {critical-chain | blame}

systemd-analyze dump

As an employer of admins for over 30 years if those admins can't be bothered to read the documentation, in man-pages or other forms, then I consider them remiss in the *most* important skill any admin should be using constantly.

When something isn't familiar you read the documentation, explore the commands themselves, do some lab-work, and become familiar with the tools.

systemd in particular has provided some excellent consistent tooling for gaining insights into service state, configuration, dependencies, resources and more.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Biting the hand that feeds IT © 1998–2019