Systemctl Command Cheat Sheet
All essential systemctl commands in one place with real usage patterns.
Basic Service Control
systemctl status nginx
systemctl start nginx
systemctl stop nginx
systemctl restart nginx
systemctl reload nginxBoot Control
systemctl enable nginx
systemctl disable nginxList Services
systemctl list-units --type=service
systemctl list-unit-filesLogs & Debugging
journalctl -u nginx
journalctl -u nginx -fReload Configuration
systemctl daemon-reloadReal Use Cases
- Service not starting → check status + journalctl
- Service not auto-start → enable
- Config changed → daemon-reload
Common Mistakes
- Forgetting enable
- Not running daemon-reload
- Ignoring logs
About this guide
This is a complete systemctl reference for real server operations. Instead of isolated commands, it provides a practical workflow covering service control, boot behavior, logs, troubleshooting, and common mistakes.
How to follow this guide
- Use systemctl status to confirm service state first.
- Use start, stop, restart depending on the situation.
- Use enable to persist service across reboot.
- Use journalctl when something fails.
- Always reload daemon after modifying service files.
Why use this method?
systemctl is the core tool for managing services on modern Linux systems. Understanding it properly allows you to control services, debug issues, and maintain stable server operations.
Frequently Asked Questions
What is systemctl?
systemctl is the command-line tool used to control systemd, which manages services and system processes on modern Linux distributions.
What is the difference between restart and reload?
restart fully stops and starts the service, while reload applies configuration changes without stopping the service if supported.
Why is my service not starting automatically?
The service may not be enabled. Use systemctl enable to configure it to start on boot.
What does daemon-reload do?
It reloads systemd configuration after you modify service files.