systemctl
The systemctl
command is a powerful utility used to interact with systemd, the init system and service manager on many Linux distributions. It allows you to manage services, system states, and various system resources.
Overview of systemctl
systemctl
systemctl
provides control over systemd services, which includes starting, stopping, restarting, enabling, disabling, and checking the status of services. Additionally, it can be used to manage system states (e.g., reboot, shutdown) and inspect logs and configurations.
General Syntax
Where:
COMMAND is the action you want to perform (e.g., start, stop, status).
NAME is the name of the service, target, or unit you want to manage (e.g.,
nginx.service
,docker
, ormulti-user.target
).
Common systemctl
Commands
systemctl
CommandsStarting a Service:
Starts a systemd service.
Example: To start the
apache2
service:
Stopping a Service:
Stops a running systemd service.
Example: To stop the
apache2
service:
Restarting a Service:
Restarts a service by stopping and then starting it again.
Example: To restart the
apache2
service:
Reloading a Service:
Reloads a service’s configuration without stopping it. Some services support reloading (like web servers).
Example: To reload the
apache2
service:
Checking the Status of a Service:
Displays the current status of a service, including whether it's running, its PID, and any recent log entries.
Example: To check the status of
apache2
:
Enabling a Service to Start at Boot:
Enables a service to start automatically when the system boots.
Example: To enable
apache2
to start at boot:
Disabling a Service from Starting at Boot:
Disables a service from automatically starting when the system boots.
Example: To disable
apache2
from starting at boot:
Masking a Service:
Prevents a service from being started, either manually or automatically, by creating a symbolic link to
/dev/null
.
Example: To mask the
apache2
service:
Unmasking a Service:
Reverses the effect of
mask
by removing the symbolic link.
Example: To unmask
apache2
:
Viewing Logs for a Service:
Displays the logs for a specific service managed by systemd.
Example: To view the logs for
apache2
:
Viewing the System Logs:
Displays the entire system journal, including messages from all services and system events.
Rebooting the System:
Reboots the entire system.
Shutting Down the System:
Shuts down the system gracefully.
Suspending the System:
Suspends the system (puts it to sleep).
Viewing All Active Units:
Lists all active systemd units (services, sockets, etc.).
Viewing All Loaded Units:
Lists all loaded systemd units, including inactive ones.
Checking Systemd Targets:
Lists the systemd targets. Targets represent different states or "runlevels" in systemd. For example,
multi-user.target
is similar to runlevel 3 in traditional SysVinit systems.
Switching Runlevels (Changing Targets):
You can switch between different systemd targets (which are similar to runlevels).
Example: To switch to the multi-user target (which is equivalent to runlevel 3):
Checking System Boot Logs:
You can view the logs related to the system’s boot process.
Example Usage
1. Start the Apache service:
2. Check the status of a service:
3. Enable a service to start at boot:
4. Disable a service from starting at boot:
5. Restart a service after making configuration changes:
6. Check all active services:
7. Reboot the system:
8. View logs for the nginx
service:
nginx
service:9. Power off the system:
Conclusion
The systemctl
command is an essential tool for managing a system running systemd. It provides control over services, targets (runlevels), and logs, enabling administrators to configure, troubleshoot, and maintain their Linux systems effectively. From simple service management to complex system configurations, systemctl
is the go-to utility for modern Linux administration.
Last updated