Master Systemd Service Management with systemctl: Start, Stop, Restart & Enable

1. What is Systemd?

Systemd is the first process (PID 1) started by Linux after boot, responsible for launching and managing all other processes. Although it is sometimes criticized for being too broad, it standardizes service management across Linux distributions.

2. Core command: systemctl

The systemctl utility is the Swiss‑army‑knife for managing services. For example, to control the nginx service you can use:

Start the service: sudo systemctl start nginx Stop the service: sudo systemctl stop nginx Restart the service: sudo systemctl restart nginx Reload configuration without interrupting the service: sudo systemctl reload nginx Check the service status: sudo systemctl status nginx (green “active (running)” means the service is up, red “failed” indicates a problem).

Two additional useful commands are:

systemctl list-units --type=service --state=running
systemctl list-unit-files --type=service | head

3. Managing boot‑time enablement

Enable a service to start at boot: sudo systemctl enable nginx Disable a service from starting at boot: sudo systemctl disable nginx Check whether a service is enabled:

sudo systemctl is-enabled nginx

4. Viewing system logs with journalctl

If a service fails to start, you can inspect its logs using journalctl:

Show all logs: journalctl Show logs for a specific service: journalctl -u nginx Follow new log entries in real time (similar to tail -f): journalctl -u nginx -f Show error‑level logs from the current boot: journalctl -b -p err Show the last 200 lines without paging: journalctl -u nginx -n 200 --no-pager Show logs since a specific time, e.g., one hour ago: journalctl -u nginx --since "1 hour ago" After modifying a service’s configuration or unit file, reload the daemon and restart the service:

sudo systemctl daemon-reload
sudo systemctl restart nginx

Mastering systemctl and journalctl gives you essential server‑operation skills.