How to Use the ‘systemctl’ Command to Manage Systemd Services

The Rise of Systemd

Modern Linux distributions (like Ubuntu, CentOS, and Debian) use a highly centralized initialization system called systemd. It is the absolute core of the operating system, responsible for booting up the machine, mounting hard drives, and launching background background services (daemons) like Apache web servers or MySQL databases.

To control this massive infrastructure, Linux administrators use a single master command: systemctl. It completely replaces the legacy service and chkconfig commands used in older versions of Linux.

1. Starting and Stopping Services

If you just installed the Nginx web server, it might not turn on automatically. You must explicitly tell systemd to launch the daemon.

sudo systemctl start nginx

If you are making changes to the website’s configuration file, Nginx will not recognize the changes until it is restarted.

sudo systemctl restart nginx

(Note: A restart forcefully kills the process and boots it back up, momentarily dropping all active connections. If you want a zero-downtime refresh where the server gracefully re-reads its configuration file without dropping current users, you should use sudo systemctl reload nginx).

2. Auditing Service Health (The Status Command)

If your web server suddenly crashes, your first troubleshooting step should always be checking the system status. This command provides an incredibly detailed diagnostic readout.

systemctl status nginx

The output will show you:

• Loaded: Is the configuration file physically present on the hard drive?
• Active: Is it currently running (green), gracefully stopped (white), or failed/crashed (red)?
• Main PID: The exact Process ID of the application.
• Recent Logs: Crucially, it prints the last 10 lines of the application’s error log directly to the terminal, often telling you exactly why the software crashed.

3. Enabling Services at Boot

Just because you used start to turn on the database does not mean it will survive a reboot. If the physical server loses power in the middle of the night and turns back on, the database will remain offline until you wake up and type start again.

To configure a service to automatically launch itself every time the operating system boots up, you must use the enable command.

sudo systemctl enable mysql

This creates the necessary symbolic links deep inside the Linux file system, guaranteeing the database always turns on automatically. To reverse this, use sudo systemctl disable mysql.

4. Masking (The Nuclear Option)

If there is a specific service that you absolutely, fundamentally never want to run (perhaps a known security vulnerability like legacy Telnet), simply “disabling” it isn’t enough. Another application could accidentally trigger it to start.

You can “mask” the service. This links the service’s boot file directly to /dev/null (the Linux black hole), making it mathematically impossible for the service to start, even if an administrator explicitly types the start command.

sudo systemctl mask telnet.socket

Conclusion

The systemctl command is the definitive control panel for modern Linux servers. By mastering its start, enable, and status arguments, administrators can ensure high availability of critical infrastructure and rapid diagnosis of crashing daemons.