Cyber Services / All lessons / CentOS / Linux Administration / About Linux OS 8 (Systemd & Services)

About Linux OS 8 (Systemd & Services)

Module 10 of 33 · 5 min read · Free to read

MODULES ↓ Command blocks have a COPY button

The Heartbeat of the Modern CentOS/RHEL Server

In modern Linux distributions like CentOS 8, the entire system—from the moment the kernel loads to the shutdown sequence—is managed by a powerful and comprehensive system and service manager called systemd. It is the first process that starts (with PID 1) and the last process that ends. Understanding systemd is not optional; it is the key to mastering the operational state of your server.

What is `systemd`? The System's General Manager

Think of systemd as the General Manager of your entire operating system. It replaces the older, slower SysVinit scripts with a fast, parallel, and dependency-aware management system. Its responsibilities are vast:

  • Initializing the System: It brings the server from a powered-off state to a fully functional, logged-in state.
  • Service Management: It starts, stops, restarts, and monitors all the background programs (daemons/services) like the web server and SSH service.
  • Unified Logging: It captures all system, service, and kernel logs in a structured binary format called the Journal.
  • And More: It also manages device mounting, network connections, scheduled tasks (timers), and system states (targets).

The Core Concept: `systemd` Units

systemd manages everything through configuration files called units. The type of unit is defined by its suffix (e.g., .service, .target).

Unit TypeWhat it isAnalogy
.serviceDefines a system service or daemon (e.g., sshd.service). This is the most common unit type you will interact with.A single worker or employee.
.targetA logical grouping of other units. It represents a system state or milestone (e.g., multi-user.target).A department or a project milestone.
.socketDefines a network socket. systemd can listen on this socket and only start the corresponding .service when a connection comes in.A telephone operator who only connects the call when someone dials the number.
.timerDefines a scheduled event, similar to `cron`, that can activate another unit.A recurring calendar appointment.

The Master Command: `systemctl`

You control nearly all aspects of systemd with the systemctl command. Its subcommands can be grouped into three logical categories.

1. Inspecting Service Status

  • status : Shows the detailed, real-time status of a unit.
    $ systemctl status sshd.service
    ● sshd.service - OpenSSH server daemon
       Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset: enabled)
       Active: active (running) since Wed 2025-08-06 10:15:23 UTC; 5h 2min ago
       ...
  • is-active : A simple check that just returns "active" or "inactive".
  • is-enabled : Checks if the service is configured to start automatically on boot.

2. Controlling Live Services (Session Only)

These commands affect the service right now but do not persist after a reboot.

# Start the Apache web server
sudo systemctl start httpd

# Stop the Apache web server
sudo systemctl stop httpd

# Restart the service (e.g., after changing its config file)
sudo systemctl restart httpd

# Reload the configuration gracefully without dropping connections
sudo systemctl reload httpd

3. Managing Services at Boot (Persistent)

These commands configure the service's behavior for all future boots.

# Configure the SSH service to start automatically on every boot
sudo systemctl enable sshd

# Prevent the SSH service from starting automatically
sudo systemctl disable sshd

# A useful shortcut to enable and start a service in one command
sudo systemctl enable --now httpd

System States: Understanding Targets

systemd uses .target units to define system states. These are the modern replacement for the old SysVinit "runlevels."

Old RunlevelNew `systemd` TargetPurpose
0poweroff.targetSystem shutdown.
1rescue.targetSingle-user, minimal rescue mode.
3multi-user.targetStandard multi-user, non-graphical (command-line) server environment.
5graphical.targetMulti-user, graphical desktop environment.
6reboot.targetSystem reboot.

You can view and change the default state your server boots into.

# Check the current default target
systemctl get-default

# Set the server to always boot into the command line
sudo systemctl set-default multi-user.target

# Temporarily switch to the graphical target without rebooting
sudo systemctl isolate graphical.target

The Unified Log: Querying with `journalctl`

systemd captures logs from all services, the kernel, and other system components into a single, structured binary log called the Journal. You query this powerful database with the journalctl command.

# View all logs, starting with the oldest (press 'q' to quit)
journalctl

# View logs for a specific service only
journalctl -u sshd.service

# Follow new logs in real-time (like `tail -f`)
journalctl -f

# Show logs from the last hour only
journalctl --since "1 hour ago"

# Jump to the end of the log and show the last 20 entries
journalctl -n 20 -e
Comprehensive Lab: Diagnosing and Fixing a Broken Service

Scenario: You've installed the Apache web server, but it won't start. You must use `systemd` tools to find and fix the problem.

  1. Install the service: sudo dnf install -y httpd
  2. Try to start it: sudo systemctl start httpd
  3. Diagnose the failure: The start command likely failed silently. Now, investigate with systemctl status httpd. It will show Active: failed and may provide a hint about the error.
  4. Get the details from the journal: The status output suggests looking at the logs. Run journalctl -u httpd.service -e. The -e flag jumps to the end, where you will find the specific error message (e.g., "Syntax error on line 55 of /etc/httpd/conf/httpd.conf").
  5. Simulate the Fix: Open the configuration file: sudo vim /etc/httpd/conf/httpd.conf. Go to the line number from the error message and correct the "typo" you (or a previous admin) made. Save and quit the file.
  6. Restart and Verify: Now that it's fixed, restart the service: sudo systemctl restart httpd. Check its status again with systemctl status httpd. It should now show Active: active (running).
  7. Make it Persistent: Enable the service to ensure your web server starts after the next reboot: sudo systemctl enable httpd.
Modules (33) ← CentOS / Linux Administration