Keep Your Services Running in the Background with SystemD

📆 · ⏳ 3 min read · ·

Introduction

SystemD is a system and service manager for Linux that provides an efficient way to manage services and daemons. SystemD can be used to start, stop, and manage services, as well as monitor their status.

By using SystemD to run your services in the background, you can ensure that they continue to run even after you log out of your system.

Run a Service in the Background with SystemD

Create a SystemD Service

To create a SystemD service, you will need to create a new service file in the /etc/systemd/system/ directory.

For example, to create a service for Apache, you can create the file /etc/systemd/system/httpd.service with the following contents:

Terminal window
[Unit]
Description=Apache Web Server
[Service]
Type=simple
ExecStart=/usr/sbin/httpd -k start
ExecStop=/usr/sbin/httpd -k stop
[Install]
WantedBy=multi-user.target

Start and Stop the Service

To start the Apache service, use the following command:

Terminal window
sudo systemctl start httpd

To stop the Apache service, use the following command:

Terminal window
sudo systemctl stop httpd

Monitor Service Status

You can monitor the status of the Apache service by using the following command:

Terminal window
systemctl status httpd

This command will show you whether the service is running or not, as well as other information about the service.

Enable and Disable Services

You can also enable and disable services so that they start automatically at boot time. To enable the Apache service, use the following command:

Terminal window
sudo systemctl enable httpd

To disable the Apache service, use the following command:

Terminal window
sudo systemctl disable httpd

Detailed Explanation

[Unit]

This section specifies metadata about the service, such as its description, dependencies, and related services.

Terminal window
Description=Apache Web Server

This line gives a description of the service, which can be any text you like. In this case, it’s “Apache Web Server.”

[Service]

This section specifies the actions that SystemD should take to start and stop the service.

Terminal window
Type=simple

This line specifies the type of service. “simple” is a common type for most services.

Terminal window
ExecStart=/usr/sbin/httpd -k start

This line specifies the command that SystemD should run to start the service. In this case, it’s /usr/sbin/httpd with the argument -k start.

Terminal window
ExecStop=/usr/sbin/httpd -k stop

This line specifies the command that SystemD should run to stop the service. In this case, it’s /usr/sbin/httpd with the argument -k stop.

[Install]

This section specifies how the service should be installed and integrated into the system.

Terminal window
WantedBy=multi-user.target

This line specifies the target that the service should be integrated with. The target multi-user.target means that the service will start automatically at boot time, after the basic system services have started.

So, that’s an overview of what each line in a SystemD service file means. By understanding each line, you can create and customize your own SystemD services to run your services in the background.

Conclusion

SystemD provides an easy and efficient way to run services in the background on Linux. By following the steps outlined in this guide, you can create a SystemD service, start and stop it, monitor its status, and enable and disable it.

Start using SystemD to manage your services and keep them running smoothly in the background.

You may also like

  • Mount a drive permanently with fstab in Linux

    Let's see how to mount a drive permanently in Linux using the fstab file which will mount the drive automatically on boot.

  • Setup Jellyfin with Hardware Acceleration on Orange Pi 5 (Rockchip RK3558)

    Recently I moved my Jellyfin to an Orange Pi 5 Plus server. The Orange Pi 5 has a Rockchip RK3558 SoC with integrated ARM Mali-G610. This guide will show you how to set up Jellyfin with hardware acceleration on the Orange Pi 5.

  • HTTPS with self-signed certificates for your Homelab services

    In this article we will deep dive into understanding how we can setup HTTPS with self-signed certificates for our Homelab services.This is often required when you are running your own services and you want to access them over HTTPS.