All the major Linux distributions, such as Ubuntu, Fedora, etc use the systemd init system today for managing and controlling various services while the system is running. In this guide, we explain the systemd commands you can use to manage systemd services using systemctl.
Table of Contents
Service management concept
Systemd is the init system and service manager of modern Linux systems. The init system is the first process that starts when you power on your system and keeps running until it is shut down.
The main purpose of systemd as init system is to initialize various system components just after the Linux kernel is booted at the beginning. Additionally, when the system is running, it also manages various services and daemons such as ssh daemon, network manager, etc.
The systemd works on the unit files. There are different types of unit files based on the purpose and resources. For example, the services have unit files with
.service extensions, whereas device unit files have
.device extensions. The systemctl command of systemd is used to manage the unit files.
Important Unit files and description
|A system service.
|A group of systemd units.
|A file system automount point.
|A device file recognized by the kernel.
|A file system mount point.
|A file or directory in a file system.
|An externally created process.
|A group of hierarchically organized units that manage system processes.
|A saved state of the systemd manager.
|An inter-process communication socket.
|A swap device or a swap file.
|A systemd timer.
Where are the unit files stored?
The unit files are stored in two places ideally in a Linux system. The files created at run time, and boot time are stored in
/run/systemd/system/. The unit files you create manually (e.g.
systemctl enable command) is stored at
/etc/systemd/system/ path takes precedence over the run time unit files present at
There is another path where systemd keeps the system’s copy of the service unit files –
Manage Systemd Services Using systemctl
First, let’s look at how you can list the services, check their status, etc. This is required if you want to understand the state of your system for investigation purposes.
To list out all systemd active units, you can use the below command.
This command gives a large output with the below headings. Scroll using arrow keys (up, down, left, and right) to view the entire output.
- UNIT – Name of the systemd unit
- Load – Reflects whether systemd parsed the config file of the unit and it is loaded in memory
- ACTIVE – Unit state (high-level status).
- SUB – Unit state (low-level status)
- DESCRIPTION – Description of the unit.
For example, the ACTIVE value can be active whereas the SUB level can be many such as running, listening, dead, and active.
More example commands:
systemctl list-units --all
systemctl list-units --all --state=inactive
To list all units of type service, use the below command.
systemctl list-units --type=service
You can combine additional parameters as well. For example, if you want to find out the services that are running, use the below command.
systemctl list-units --type=service --state=running
The other combinations of
state values which you can use are –
Additionally, you can list all unit files using the below commands.
Managing unit files are a different topic which I will cover in the next article.
Show Service Status
To find out the status of a service, use the
below command. For this guide, I have used the
NetworkManager service, which controls the network management of a system. You can replace the NetworkManager with your own service name. All the following commands require sudo privilege. If you do not know the service name, check the above commands to display all service units, then filter out using the
systemctl status NetworkManager.service
Note that you can omit the .service at the end of the service name. The systemd is clever enough to understand the command!
In the above example, you can see all information is provided in the command. It also has the CGroup value to identify the user groups, which is needed in a server environment.
Some more example commands:
systemctl is-active NetworkManager.service
systemctl is-enabled NetworkManager.service
systemctl is-failed NetworkManager.service
Start a service
Starting a systemd service is easy. Run the below command with start and service name. The command starts the service.
sudo systemctl start NetworkManager.service
Stop a service
Using the stop parameter, you can stop a service. For example:
sudo systemctl stop NetworkManager.service
Be cautious while stopping a service. Make sure you know what you are doing.
Restart and reload a service
The systemd provides options to configure a service so that it can restart or reload without restarts. The restart parameter restarts the services, and the reload uses configuration files
sudo systemctl restart NetworkManager.service
sudo systemctl reload NetworkManager.service
Enable and disable a service
If you created a new service or installed applications that work via services, starting them using the start command will not enable it again in the next boot. So, if you want the systemd to start a service when the system boots, you need to use the enable command. The same is true for disabling when you want to disable a service at boot time.
sudo systemctl enable NetworkManager.service
The enable command creates a symlink from /etc/systemd/system to the target locations.
To disable the service, use the below command.
sudo systemctl disable NetworkManager.service
The systemd services and their associated commands have many additional options as well. The systemd is a robust and important component of modern Linux systems. I hope this guide helps you to troubleshoot your desktop or servers when required in Linux. There are many additional features that systemd provides – such as target files, modifying the service unit files, etc. – which I will cover in the next set of articles. All the articles are tagged with systemd for easy browsing.