The systemd unit file is a configuration file that defines the behavior of the system resource and is used to control the process at startup and runtime. It is divided into three main parts: [Unit], [Service], and [Install], which describe metadata and dependencies, service execution methods, and enable methods. Common locations include /usr/lib/systemd/system/, /etc/systemd/system/, /run/systemd/system/. Viewing and editing can be achieved through text tools or systemctl edit command, and systemctl daemon-reload needs to be executed to take effect. When a custom service or script is required to run automatically, a new unit file should be created.

A systemd unit file is a configuration file that defines how a service, socket, device, or other system resource should behave when managed by systemd. These files are essential for controlling processes during system startup and runtime. They specify dependencies, execution methods, and conditions under which the unit should run.

Understanding What a Unit File Contains

Unit files are plain text files with a structured format divided into sections. The most common sections are:

• [Unit] : Describes metadata and dependencies (like description, after which services it should start).
• [Service] : Defines how the service should be run (start command, restart behavior, user, etc.).
• [Install] : Specifies how the unit should be enabled or started automatically at boot.

For example, a simple service unit file might include a line like ExecStart=/usr/bin/myprogram to tell systemd what command to run when starting the service.

These files help systemd understand not just what to run, but also when and how to manage it.

Common Locations for Unit Files

Systemd looks for unit files in specific directories. The main ones you'll encounter are:

• /usr/lib/systemd/system/ – This is where most default unit files from installed packages live.
• /etc/systemd/system/ – User-created or customized unit files go here. Changes made in this directory take precedence over the ones in /usr/lib .
• /run/systemd/system/ – Temporary unit files stored in memory; they disappear after reboot.

If you're modifying or creating your own unit file, /etc/systemd/system/ is usually the right place to put it.

How to View and Edit Unit Files

You can look at existing unit files using standard tools like cat , less , or any text editor. For example:

 cat /usr/lib/systemd/system/sshd.service

This shows how the SSH daemon is configured.

If you want to override part of a unit file without replacing the whole thing, use systemctl edit myservice.service . That creates a drop-in file in /etc/systemd/system/ that only changes what you specify.

After editing, always reload systemd:

 systemctl daemon-reload

When You Might Need to Create One

You don't always need to write a unit file — most services come with them. But if you're running a custom script or application that needs to start on boot or restart automatically, writing a unit file makes sense.

For example, if you have a background Python script you want to run as a service, you'd create a .service file in /etc/systemd/system/ that tells systemd how to handle it.

It doesn't have to be complex — just enough to define the basics like what to run, under which user, and whether to restart if it fails.

Basically that's it.

The above is the detailed content of What is a systemd unit file and where is it located?. For more information, please follow other related articles on the PHP Chinese website!