Learn how Linux starts, stops, restarts, enables, disables, and monitors background services using systemd and systemctl. Think of this module as your Linux server control room. 🚦
A Linux server is like a building. Many workers run in the background: SSH, web server, database, logging, networking, firewall, monitoring. Somebody must start them, stop them, watch them, and decide who reports for duty when the building opens. That “somebody” is systemd.
| Linux term | Beginner analogy | Real meaning |
|---|---|---|
| systemd | Building manager 🧑💼 | The init system and service manager used by most modern Linux distributions. |
| service unit | A worker 👷 | A background program managed by systemd, such as SSH or Apache. |
| systemctl | Control room remote 🎛️ | The command used to control and inspect systemd services. |
| start | Tell worker to begin ▶️ | Run a service right now. |
| enable | Add to morning duty roster 🚀 | Configure service to start automatically during boot. |
| status | Ask “are you okay?” 🩺 | Show whether the service is running, failed, stopped, and recent logs. |
Linux kernel starts first.
It becomes process ID 1.
Services, sockets, mounts, timers are read.
Networking before network services, disks before mounts.
Enabled services start automatically.
Service management has two separate questions: is the service running now? and should it start automatically after reboot? Beginners often mix these up. Keep them separate and everything becomes easier.
systemd manages Linux startup and background units. It starts services in the correct order based on dependencies.
systemctl is the command-line tool used to inspect and control systemd units.
A service unit usually ends with .service, for example sshd.service, nginx.service, or NetworkManager.service.
start means “run now”; enable means “run at boot.” One controls the present. The other controls the next reboot.
systemctl status sshd
sudo systemctl start sshd
sudo systemctl stop sshd
sudo systemctl restart sshdThese commands affect the current running state.
sudo systemctl enable sshd
sudo systemctl disable sshd
systemctl is-enabled sshd
systemctl list-unit-files --type=service --state=enabledThese commands control whether services start automatically after reboot.
At boot time, systemd checks what services are enabled, works out dependencies, then starts them in the correct order. The animation below shows the simplified flow.
Click the buttons. Watch the fake service move between common states. This teaches the logic before students touch a real server.
The service is currently running.
$ systemctl status demo.service
● demo.service - Demo Service
Loaded: loaded (/etc/systemd/system/demo.service; enabled)
Active: active (running)
Beginner note: active means the service is running now.These are the daily-use service commands. Read the purpose, run the command, then compare the expected output.
systemctl status sshdPurpose: Shows whether the service is running, stopped, failed, enabled, disabled, and recent log lines.
Look for Active: active (running). If it says failed, read the log lines shown below the status.
sudo systemctl restart sshdPurpose: Stops and starts a service again. Useful after config changes, but risky if the config is broken.
Usually no output means success. Confirm with systemctl status sshd.
sudo systemctl enable sshdPurpose: Makes the service start automatically when Linux boots.
enable does not mean “start right now.” It configures future boot behavior. Use start or restart for the current running state.
systemctl is-enabled sshdPurpose: Shows whether the service is enabled, disabled, static, masked, or indirect.
enabled = starts at boot. disabled = does not start automatically. static = cannot be enabled directly. masked = blocked from starting.
This is a common lab issue. RHEL-family systems usually use sshd. Ubuntu/Debian systems usually use ssh. Teach both so students do not get stuck on “Unit sshd.service could not be found.”
systemctl status sshd
sudo systemctl restart sshd
sudo systemctl enable sshd
systemctl is-enabled sshdsystemctl status ssh
sudo systemctl restart ssh
sudo systemctl enable ssh
systemctl is-enabled sshsystemctl list-unit-files | grep -E '^(ssh|sshd)\.service'
systemctl list-units --type=service | grep -E 'ssh|sshd'Labs are arranged from safe inspection to real service control. SSH labs are included because that is the requested module lab, but the custom demo service is safer for repeated start/stop experiments.
Goal: learn how to read whether a service is active, failed, or stopped.
systemctl status sshdsystemctl status ssh● sshd.service - OpenSSH server daemon
Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
Active: active (running) since Mon 2026-08-03 09:30:22 IST
Main PID: 1052 (sshd)Focus on Loaded:, Active:, and recent log lines. Beginners should not try to understand every field on day one.
Goal: restart a service and verify it returned to running state.
sudo systemctl restart sshd
systemctl status sshd --no-pagersudo systemctl restart ssh
systemctl status ssh --no-pagerThe restart command usually prints nothing on success. The status command should show Active: active (running).
Goal: configure SSH to start automatically after reboot and verify the boot setting.
sudo systemctl enable sshd
systemctl is-enabled sshdsudo systemctl enable ssh
systemctl is-enabled sshenabledGoal: create, start, enable, inspect, and clean up a custom systemd service.
This script writes a timestamp every 5 seconds. It gives us a harmless service to control.
sudo tee /usr/local/bin/hello-systemd.sh >/dev/null <<'SCRIPT'
#!/usr/bin/env bash
while true; do
echo "Hello from systemd at $(date)"
sleep 5
done
SCRIPT
sudo chmod +x /usr/local/bin/hello-systemd.shThe unit tells systemd what to run and when it can start.
sudo tee /etc/systemd/system/hello.service >/dev/null <<'UNIT'
[Unit]
Description=Beginner Hello Service
After=network.target
[Service]
Type=simple
ExecStart=/usr/local/bin/hello-systemd.sh
Restart=always
RestartSec=2
[Install]
WantedBy=multi-user.target
UNITdaemon-reload tells systemd to read new or changed unit files.
sudo systemctl daemon-reload
sudo systemctl start hello
systemctl status hello --no-pagerLogs come from stdout/stderr and are stored in the journal.
journalctl -u hello -n 10 --no-pager
sudo systemctl enable hello
systemctl is-enabled helloAlways clean lab artifacts so the VM stays tidy.
sudo systemctl disable --now hello
sudo rm -f /etc/systemd/system/hello.service /usr/local/bin/hello-systemd.sh
sudo systemctl daemon-reload
sudo systemctl reset-failed helloGoal: learn how service failures appear and how to investigate them.
sudo tee /etc/systemd/system/broken-demo.service >/dev/null <<'UNIT'
[Unit]
Description=Broken Demo Service
[Service]
Type=simple
ExecStart=/wrong/path/does-not-exist.sh
[Install]
WantedBy=multi-user.target
UNIT
sudo systemctl daemon-reloadsudo systemctl start broken-demo || true
systemctl status broken-demo --no-pager
journalctl -u broken-demo -n 20 --no-pagerYou should see a failure message similar to “No such file or directory” because ExecStart points to a path that does not exist.
sudo systemctl reset-failed broken-demo
sudo rm -f /etc/systemd/system/broken-demo.service
sudo systemctl daemon-reloadGoal: compare “configured to start at boot” with “running right now.”
systemctl list-unit-files --type=service --state=enabledsystemctl list-units --type=service --state=running| Command | Answers this question |
|---|---|
list-unit-files | What is installed/configured, and what is its boot-time state? |
list-units | What units are currently loaded into systemd memory? |
These mistakes are normal. The trick is to teach the correction immediately.
| Mistake | Correction |
|---|---|
| “start and enable are same.” | No. start runs now. enable starts at boot. |
| “restart always fixes it.” | No. If configuration is wrong, restart can fail. Check status and journalctl. |
| “disable stops the service.” | No. disable only prevents automatic start during boot. Use stop to stop now. |
| “sshd works everywhere.” | No. RHEL/Rocky usually use sshd; Ubuntu usually uses ssh. |
| “status only says running or not.” | It also shows loaded unit file, boot state, PID, memory, tasks, and recent logs. |
Suggested flow for a beginner classroom session.
Ask: “Which background workers are needed on a server?” Collect examples: SSH, web, database, logs, firewall.
Show systemctl status sshd or systemctl status ssh. Do not start with service file syntax.
Ask the class: “What is the difference between running now and enabled at boot?”
Let students create hello.service, then start, enable, inspect logs, and clean up.
Break broken-demo.service. Students must identify the error using status and journalctl.
Tick each item while practicing. Progress is saved in this browser.
Use this as a recap after the labs. No pressure — just small brain push-ups. 🧠
systemctl status usually tells whether a service is running?start and enable?systemctl status show?hello.service and enable it.Keep this section open during labs. It is the fast reference.
| Task | RHEL/Rocky | Ubuntu/Debian |
|---|---|---|
| Check SSH status | systemctl status sshd | systemctl status ssh |
| Restart SSH | sudo systemctl restart sshd | sudo systemctl restart ssh |
| Enable SSH at boot | sudo systemctl enable sshd | sudo systemctl enable ssh |
| Check boot setting | systemctl is-enabled sshd | systemctl is-enabled ssh |
| View logs | journalctl -u sshd -n 50 --no-pager | journalctl -u ssh -n 50 --no-pager |
# Replace SERVICE with sshd, ssh, nginx, httpd, NetworkManager, etc.
systemctl status SERVICE
sudo systemctl start SERVICE
sudo systemctl stop SERVICE
sudo systemctl restart SERVICE
sudo systemctl enable SERVICE
sudo systemctl disable SERVICE
systemctl is-enabled SERVICE
journalctl -u SERVICE -n 50 --no-pagersystemctl restart usually means success. Verify with status.