Mastering systemd: How to Create, Configure, and Manage Custom Linux Services

Introduction

systemd is the default init system and service manager on modern Linux distributions. It handles system boot tasks, process supervision, and logging, and allows users to define custom services for specific tasks.

Creating a Service Unit File

To define a new service, create a unit file with a .service extension under /etc/systemd/system. A basic unit file contains three sections: [Unit]: metadata such as Description and dependencies. [Service]: execution parameters like ExecStart, Type, Restart, etc. [Install]: installation information such as WantedBy.

Example:

[Unit]
Description=My Custom Service
After=network.target

[Service]
Type=simple
ExecStart=/usr/local/bin/my_service
Restart=always

[Install]
WantedBy=multi-user.target

Configuring the Service

1. File Permissions and Paths

Ensure the executable has proper permissions and resides in a standard location such as /usr/local/bin or /opt.

sudo chmod +x /usr/local/bin/my_service

2. Environment Variables

Set variables directly in the unit file with Environment= or load them from a file with EnvironmentFile=.

[Service]
Environment="VAR1=value1"
Environment="VAR2=value2"

[Service]
EnvironmentFile=/etc/my_service.env

3. Logging

Redirect service output to the system log using StandardOutput and StandardError.

[Service]
StandardOutput=syslog
StandardError=syslog

Starting and Managing the Service

Use systemctl to control the service.

Start: sudo systemctl start servicename Stop: sudo systemctl stop servicename Restart: sudo systemctl restart servicename Status:

sudo systemctl status servicename

Advanced Usage

1. Pre‑ and Post‑Execution Hooks

Define commands that run before or after start/stop with ExecStartPre, ExecStartPost, ExecStop, and ExecStopPost.

[Service]
ExecStartPre=/bin/mkdir -p /var/run/my_service
ExecStartPost=/bin/chmod 755 /var/run/my_service
ExecStop=/bin/rm -rf /var/run/my_service
ExecStopPost=/bin/rmdir /var/run/my_service

2. Resource Limits

Limit CPU, memory, and task count with directives such as CPUShares, MemoryLimit, and TasksMax.

[Service]
CPUShares=512
MemoryLimit=1G
TasksMax=1000

3. Private Temporary Filesystem

Enable an isolated /tmp for the service with PrivateTmp=yes.

[Service]
PrivateTmp=yes

4. System Logging

Configure StandardOutput and StandardError to syslog so that all output is captured by the system logger.

[Service]
StandardOutput=syslog
StandardError=syslog

Complete Example

A full unit file that runs a simple script:

[Unit]
Description=My Custom Service
After=network.target

[Service]
Type=simple
ExecStart=/usr/local/bin/my_script.sh
Restart=always

[Install]
WantedBy=multi-user.target

The script /usr/local/bin/my_script.sh could contain:

#!/bin/bash
echo "Hello, world!" >> /var/log/my_service.log

Conclusion

By creating and configuring systemd unit files, Linux administrators can reliably manage custom services, control their lifecycle, apply resource constraints, and integrate with the system journal, making systemd a powerful and flexible tool for service management.