{"id":4559,"date":"2022-12-20T18:09:04","date_gmt":"2022-12-20T21:09:04","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/systemd-service-man5\/"},"modified":"2022-12-20T18:09:04","modified_gmt":"2022-12-20T21:09:04","slug":"systemd-service-man5","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/systemd-service-man5\/","title":{"rendered":"SYSTEMD.SERVICE (man5)"},"content":{"rendered":"

SYSTEMD.SERVICE<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
SERVICE TEMPLATES<\/a>
AUTOMATIC DEPENDENCIES<\/a>
OPTIONS<\/a>
COMMAND LINES<\/a>
EXAMPLES<\/a>
SEE ALSO<\/a>
NOTES<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

systemd.service \u2212 Service unit configuration<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

service<\/i>.service<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

A unit configuration file whose name ends in “.service” encodes information about a process controlled and supervised by systemd.<\/p>\n

This man page lists the configuration options specific to this unit type. See systemd.unit<\/b>(5) for the common options of all unit configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The service specific configuration options are configured in the [Service] section.<\/p>\n

Additional options are listed in systemd.exec<\/b>(5), which define the execution environment the commands are executed in, and in systemd.kill<\/b>(5), which define the way the processes of the service are terminated, and in systemd.resource-control<\/b>(5), which configure resource control settings for the processes of the service.<\/p>\n

If a service is requested under a certain name but no unit configuration file is found, systemd looks for a SysV init script by the same name (with the .service suffix removed) and dynamically creates a service unit from that script. This is useful for compatibility with SysV. Note that this compatibility is quite comprehensive but not 100%. For details about the incompatibilities, see the Incompatibilities with SysV<\/font><\/b> [1]<\/font><\/small> document.<\/font><\/p>\n

The systemd-run<\/b>(1) command allows creating .service and .scope units dynamically and transiently from the command line.<\/font><\/p>\n

SERVICE TEMPLATES <\/a> <\/h2>\n

It is possible for systemd<\/b> services to take a single argument via the “service<\/i>@argument<\/i>.service” syntax. Such services are called “instantiated” services, while the unit definition without the argument<\/i> parameter is called a “template”. An example could be a dhcpcd@.service service template which takes a network interface as a parameter to form an instantiated service. Within the service file, this parameter or “instance name” can be accessed with %\u2212specifiers. See systemd.unit<\/b>(5) for details.<\/font><\/p>\n

AUTOMATIC DEPENDENCIES <\/a> <\/h2>\n

Implicit Dependencies<\/b>
The following dependencies are implicitly added:<\/font><\/p>\n

\u2022 Services with Type=dbus<\/i> set automatically acquire dependencies of type Requires=<\/i> and After=<\/i> on dbus.socket.<\/font><\/p>\n

\u2022 Socket activated services are automatically ordered after their activating .socket units via an automatic After=<\/i> dependency. Services also pull in all .socket units listed in Sockets=<\/i> via automatic Wants=<\/i> and After=<\/i> dependencies.<\/font><\/p>\n

Additional implicit dependencies may be added as result of execution and resource control parameters as documented in systemd.exec<\/b>(5) and systemd.resource-control<\/b>(5).<\/font><\/p>\n

Default Dependencies<\/b>
The following dependencies are added unless DefaultDependencies=no<\/i> is set:<\/font><\/p>\n

\u2022 Service units will have dependencies of type Requires=<\/i> and After=<\/i> on sysinit.target, a dependency of type After=<\/i> on basic.target as well as dependencies of type Conflicts=<\/i> and Before=<\/i> on shutdown.target. These ensure that normal service units pull in basic system initialization, and are terminated cleanly prior to system shutdown. Only services involved with early boot or late system shutdown should disable this option.<\/font><\/p>\n

\u2022 Instanced service units (i.e. service units with an “@” in their name) are assigned by default a per\u2212template slice unit (see systemd.slice<\/b>(5)), named after the template unit, containing all instances of the specific template. This slice is normally stopped at shutdown, together with all template instances. If that is not desired, set DefaultDependencies=no<\/i> in the template unit, and either define your own per\u2212template slice unit file that also sets DefaultDependencies=no<\/i>, or set Slice=system.slice<\/i> (or another suitable slice) in the template unit. Also see systemd.resource-control<\/b>(5).<\/font><\/p>\n

OPTIONS <\/a> <\/h2>\n

Service files must include a [Service] section, which carries information about the service and the process it supervises. A number of options that may be used in this section are shared with other unit types. These options are documented in systemd.exec<\/b>(5), systemd.kill<\/b>(5) and systemd.resource-control<\/b>(5). The options specific to the [Service] section of service units are the following:<\/font><\/p>\n

Type=<\/i><\/font><\/p>\n

Configures the process start\u2212up type for this service unit. One of simple<\/b>, exec<\/b>, forking<\/b>, oneshot<\/b>, dbus<\/b>, notify<\/b> or idle<\/b>:<\/font><\/p>\n

\u2022 If set to simple<\/b> (the default if ExecStart=<\/i> is specified but neither Type=<\/i> nor BusName=<\/i> are), the service manager will consider the unit started immediately after the main service process has been forked off. It is expected that the process configured with ExecStart=<\/i> is the main process of the service. In this mode, if the process offers functionality to other processes on the system, its communication channels should be installed before the service is started up (e.g. sockets set up by systemd, via socket activation), as the service manager will immediately proceed starting follow\u2212up units, right after creating the main service process, and before executing the service’s binary. Note that this means systemctl start<\/b> command lines for simple<\/b> services will report success even if the service’s binary cannot be invoked successfully (for example because the selected User=<\/i> doesn’t exist, or the service binary is missing).<\/font><\/p>\n

\u2022 The exec<\/b> type is similar to simple<\/b>, but the service manager will consider the unit started immediately after the main service binary has been executed. The service manager will delay starting of follow\u2212up units until that point. (Or in other words: simple<\/b> proceeds with further jobs right after fork()<\/b> returns, while exec<\/b> will not proceed before both fork()<\/b> and execve()<\/b> in the service process succeeded.) Note that this means systemctl start<\/b> command lines for exec<\/b> services will report failure when the service’s binary cannot be invoked successfully (for example because the selected User=<\/i> doesn’t exist, or the service binary is missing).<\/font><\/p>\n

\u2022 If set to forking<\/b>, it is expected that the process configured with ExecStart=<\/i> will call fork()<\/b> as part of its start\u2212up. The parent process is expected to exit when start\u2212up is complete and all communication channels are set up. The child continues to run as the main service process, and the service manager will consider the unit started when the parent process exits. This is the behavior of traditional UNIX services. If this setting is used, it is recommended to also use the PIDFile=<\/i> option, so that systemd can reliably identify the main process of the service. systemd will proceed with starting follow\u2212up units as soon as the parent process exits.<\/font><\/p>\n

\u2022 Behavior of oneshot<\/b> is similar to simple<\/b>; however, the service manager will consider the unit up after the main process exits. It will then start follow\u2212up units. RemainAfterExit=<\/i> is particularly useful for this type of service. Type=<\/i>oneshot<\/b> is the implied default if neither Type=<\/i> nor ExecStart=<\/i> are specified. Note that if this option is used without RemainAfterExit=<\/i> the service will never enter “active” unit state, but directly transition from “activating” to “deactivating” or “dead” since no process is configured that shall run continuously. In particular this means that after a service of this type ran (and which has RemainAfterExit=<\/i> not set) it will not show up as started afterwards, but as dead.<\/font><\/p>\n

\u2022 Behavior of dbus<\/b> is similar to simple<\/b>; however, it is expected that the service acquires a name on the D\u2212Bus bus, as configured by BusName=<\/i>. systemd will proceed with starting follow\u2212up units after the D\u2212Bus bus name has been acquired. Service units with this option configured implicitly gain dependencies on the dbus.socket unit. This type is the default if BusName=<\/i> is specified. A service unit of this type is considered to be in the activating state until the specified bus name is acquired. It is considered activated while the bus name is taken. Once the bus name is released the service is considered being no longer functional which has the effect that the service manager attempts to terminate any remaining processes belonging to the service. Services that drop their bus name as part of their shutdown logic thus should be prepared to receive a SIGTERM<\/b> (or whichever signal is configured in KillSignal=<\/i>) as result.<\/font><\/p>\n

\u2022 Behavior of notify<\/b> is similar to exec<\/b>; however, it is expected that the service sends a notification message via sd_notify<\/b>(3) or an equivalent call when it has finished starting up. systemd will proceed with starting follow\u2212up units after this notification message has been sent. If this option is used, NotifyAccess=<\/i> (see below) should be set to open access to the notification socket provided by systemd. If NotifyAccess=<\/i> is missing or set to none<\/b>, it will be forcibly set to main<\/b>.<\/font><\/p>\n

\u2022 Behavior of idle<\/b> is very similar to simple<\/b>; however, actual execution of the service program is delayed until all active jobs are dispatched. This may be used to avoid interleaving of output of shell services with the status output on the console. Note that this type is useful only to improve console output, it is not useful as a general unit ordering tool, and the effect of this service type is subject to a 5s timeout, after which the service program is invoked anyway.<\/font><\/p>\n

It is generally recommended to use Type=<\/i>simple<\/b> for long\u2212running services whenever possible, as it is the simplest and fastest option. However, as this service type won’t propagate service start\u2212up failures and doesn’t allow ordering of other units against completion of initialization of the service (which for example is useful if clients need to connect to the service through some form of IPC, and the IPC channel is only established by the service itself \u2014 in contrast to doing this ahead of time through socket or bus activation or similar), it might not be sufficient for many cases. If so, notify<\/b> or dbus<\/b> (the latter only in case the service provides a D\u2212Bus interface) are the preferred options as they allow service program code to precisely schedule when to consider the service started up successfully and when to proceed with follow\u2212up units. The notify<\/b> service type requires explicit support in the service codebase (as sd_notify()<\/b> or an equivalent API needs to be invoked by the service at the appropriate time) \u2014 if it’s not supported, then forking<\/b> is an alternative: it supports the traditional UNIX service start\u2212up protocol. Finally, exec<\/b> might be an option for cases where it is enough to ensure the service binary is invoked, and where the service binary itself executes no or little initialization on its own (and its initialization is unlikely to fail). Note that using any type other than simple<\/b> possibly delays the boot process, as the service manager needs to wait for service initialization to complete. It is hence recommended not to needlessly use any types other than simple<\/b>. (Also note it is generally not recommended to use idle<\/b> or oneshot<\/b> for long\u2212running services.)<\/font><\/p>\n

RemainAfterExit=<\/i><\/font><\/p>\n

Takes a boolean value that specifies whether the service shall be considered active even when all its processes exited. Defaults to no<\/b>.<\/font><\/p>\n

GuessMainPID=<\/i><\/font><\/p>\n

Takes a boolean value that specifies whether systemd should try to guess the main PID of a service if it cannot be determined reliably. This option is ignored unless Type=forking<\/b> is set and PIDFile=<\/b> is unset because for the other types or with an explicitly configured PID file, the main PID is always known. The guessing algorithm might come to incorrect conclusions if a daemon consists of more than one process. If the main PID cannot be determined, failure detection and automatic restarting of a service will not work reliably. Defaults to yes<\/b>.<\/font><\/p>\n

PIDFile=<\/i><\/font><\/p>\n

Takes a path referring to the PID file of the service. Usage of this option is recommended for services where Type=<\/i> is set to forking<\/b>. The path specified typically points to a file below \/run\/. If a relative path is specified it is hence prefixed with \/run\/. The service manager will read the PID of the main process of the service from this file after start\u2212up of the service. The service manager will not write to the file configured here, although it will remove the file after the service has shut down if it still exists. The PID file does not need to be owned by a privileged user, but if it is owned by an unprivileged user additional safety restrictions are enforced: the file may not be a symlink to a file owned by a different user (neither directly nor indirectly), and the PID file must refer to a process already belonging to the service.<\/font><\/p>\n

BusName=<\/i><\/font><\/p>\n

Takes a D\u2212Bus bus name that this service is reachable as. This option is mandatory for services where Type=<\/i> is set to dbus<\/b>.<\/font><\/p>\n

ExecStart=<\/i><\/font><\/p>\n

Commands with their arguments that are executed when this service is started. The value is split into zero or more command lines according to the rules described below (see section “Command Lines” below).<\/font><\/p>\n

Unless Type=<\/i> is oneshot<\/b>, exactly one command must be given. When Type=oneshot<\/i> is used, zero or more commands may be specified. Commands may be specified by providing multiple command lines in the same directive, or alternatively, this directive may be specified more than once with the same effect. If the empty string is assigned to this option, the list of commands to start is reset, prior assignments of this option will have no effect. If no ExecStart=<\/i> is specified, then the service must have RemainAfterExit=yes<\/i> and at least one ExecStop=<\/i> line set. (Services lacking both ExecStart=<\/i> and ExecStop=<\/i> are not valid.)<\/font><\/p>\n

For each of the specified commands, the first argument must be either an absolute path to an executable or a simple file name without any slashes. Optionally, this filename may be prefixed with a number of special characters:<\/font><\/p>\n

Table\u00a01.\u00a0Special executable prefixes<\/b><\/font><\/p>\n

\"Image<\/b><\/font><\/p>\n

“@”, “\u2212”, “:”, and one of “+”\/”!”\/”!!” may be used together and they can appear in any order. However, only one of “+”, “!”, “!!” may be used at a time. Note that these prefixes are also supported for the other command line settings, i.e. ExecStartPre=<\/i>, ExecStartPost=<\/i>, ExecReload=<\/i>, ExecStop=<\/i> and ExecStopPost=<\/i>.<\/font><\/p>\n

If more than one command is specified, the commands are invoked sequentially in the order they appear in the unit file. If one of the commands fails (and is not prefixed with “\u2212”), other lines are not executed, and the unit is considered failed.<\/font><\/p>\n

Unless Type=forking<\/i> is set, the process started via this command line will be considered the main process of the daemon.<\/font><\/p>\n

ExecStartPre=<\/i>, ExecStartPost=<\/i><\/font><\/p>\n

Additional commands that are executed before or after the command in ExecStart=<\/i>, respectively. Syntax is the same as for ExecStart=<\/i>, except that multiple command lines are allowed and the commands are executed one after the other, serially.<\/font><\/p>\n

If any of those commands (not prefixed with “\u2212”) fail, the rest are not executed and the unit is considered failed.<\/font><\/p>\n

ExecStart=<\/i> commands are only run after all ExecStartPre=<\/i> commands that were not prefixed with a “\u2212” exit successfully.<\/font><\/p>\n

ExecStartPost=<\/i> commands are only run after the commands specified in ExecStart=<\/i> have been invoked successfully, as determined by Type=<\/i> (i.e. the process has been started for Type=simple<\/i> or Type=idle<\/i>, the last ExecStart=<\/i> process exited successfully for Type=oneshot<\/i>, the initial process exited successfully for Type=forking<\/i>, “READY=1” is sent for Type=notify<\/i>, or the BusName=<\/i> has been taken for Type=dbus<\/i>).<\/font><\/p>\n

Note that ExecStartPre=<\/i> may not be used to start long\u2212running processes. All processes forked off by processes invoked via ExecStartPre=<\/i> will be killed before the next service process is run.<\/font><\/p>\n

Note that if any of the commands specified in ExecStartPre=<\/i>, ExecStart=<\/i>, or ExecStartPost=<\/i> fail (and are not prefixed with “\u2212”, see above) or time out before the service is fully up, execution continues with commands specified in ExecStopPost=<\/i>, the commands in ExecStop=<\/i> are skipped.<\/font><\/p>\n

Note that the execution of ExecStartPost=<\/i> is taken into account for the purpose of Before=<\/i>\/After=<\/i> ordering constraints.<\/font><\/p>\n

ExecCondition=<\/i><\/font><\/p>\n

Optional commands that are executed before the command(s) in ExecStartPre=<\/i>. Syntax is the same as for ExecStart=<\/i>, except that multiple command lines are allowed and the commands are executed one after the other, serially.<\/font><\/p>\n

The behavior is like an ExecStartPre=<\/i> and condition check hybrid: when an ExecCondition=<\/i> command exits with exit code 1 through 254 (inclusive), the remaining commands are skipped and the unit is not<\/i> marked as failed. However, if an ExecCondition=<\/i> command exits with 255 or abnormally (e.g. timeout, killed by a signal, etc.), the unit will be considered failed (and remaining commands will be skipped). Exit code of 0 or those matching SuccessExitStatus=<\/i> will continue execution to the next command(s).<\/font><\/p>\n

The same recommendations about not running long\u2212running processes in ExecStartPre=<\/i> also applies to ExecCondition=<\/i>. ExecCondition=<\/i> will also run the commands in ExecStopPost=<\/i>, as part of stopping the service, in the case of any non\u2212zero or abnormal exits, like the ones described above.<\/font><\/p>\n

ExecReload=<\/i><\/font><\/p>\n

Commands to execute to trigger a configuration reload in the service. This argument takes multiple command lines, following the same scheme as described for ExecStart=<\/i> above. Use of this setting is optional. Specifier and environment variable substitution is supported here following the same scheme as for ExecStart=<\/i>.<\/font><\/p>\n

One additional, special environment variable is set: if known, $MAINPID<\/i> is set to the main process of the daemon, and may be used for command lines like the following:<\/font><\/p>\n

ExecReload=kill \u2212HUP $MAINPID<\/font><\/p>\n

Note however that reloading a daemon by sending a signal (as with the example line above) is usually not a good choice, because this is an asynchronous operation and hence not suitable to order reloads of multiple services against each other. It is strongly recommended to set ExecReload=<\/i> to a command that not only triggers a configuration reload of the daemon, but also synchronously waits for it to complete. For example, dbus-broker<\/b>(1) uses the following:<\/font><\/p>\n

ExecReload=busctl call org.freedesktop.DBus
\/org\/freedesktop\/DBus org.freedesktop.DBus
ReloadConfig<\/font><\/p>\n

ExecStop=<\/i><\/font><\/p>\n

Commands to execute to stop the service started via ExecStart=<\/i>. This argument takes multiple command lines, following the same scheme as described for ExecStart=<\/i> above. Use of this setting is optional. After the commands configured in this option are run, it is implied that the service is stopped, and any processes remaining for it are terminated according to the KillMode=<\/i> setting (see systemd.kill<\/b>(5)). If this option is not specified, the process is terminated by sending the signal specified in KillSignal=<\/i> or RestartKillSignal=<\/i> when service stop is requested. Specifier and environment variable substitution is supported (including $MAINPID<\/i>, see above).<\/font><\/p>\n

Note that it is usually not sufficient to specify a command for this setting that only asks the service to terminate (for example, by sending some form of termination signal to it), but does not wait for it to do so. Since the remaining processes of the services are killed according to KillMode=<\/i> and KillSignal=<\/i> or RestartKillSignal=<\/i> as described above immediately after the command exited, this may not result in a clean stop. The specified command should hence be a synchronous operation, not an asynchronous one.<\/font><\/p>\n

Note that the commands specified in ExecStop=<\/i> are only executed when the service started successfully first. They are not invoked if the service was never started at all, or in case its start\u2212up failed, for example because any of the commands specified in ExecStart=<\/i>, ExecStartPre=<\/i> or ExecStartPost=<\/i> failed (and weren’t prefixed with “\u2212”, see above) or timed out. Use ExecStopPost=<\/i> to invoke commands when a service failed to start up correctly and is shut down again. Also note that the stop operation is always performed if the service started successfully, even if the processes in the service terminated on their own or were killed. The stop commands must be prepared to deal with that case. $MAINPID<\/i> will be unset if systemd knows that the main process exited by the time the stop commands are called.<\/font><\/p>\n

Service restart requests are implemented as stop operations followed by start operations. This means that ExecStop=<\/i> and ExecStopPost=<\/i> are executed during a service restart operation.<\/font><\/p>\n

It is recommended to use this setting for commands that communicate with the service requesting clean termination. For post\u2212mortem clean\u2212up steps use ExecStopPost=<\/i> instead.<\/font><\/p>\n

ExecStopPost=<\/i><\/font><\/p>\n

Additional commands that are executed after the service is stopped. This includes cases where the commands configured in ExecStop=<\/i> were used, where the service does not have any ExecStop=<\/i> defined, or where the service exited unexpectedly. This argument takes multiple command lines, following the same scheme as described for ExecStart=<\/i>. Use of these settings is optional. Specifier and environment variable substitution is supported. Note that \u2013 unlike ExecStop=<\/i> \u2013 commands specified with this setting are invoked when a service failed to start up correctly and is shut down again.<\/font><\/p>\n

It is recommended to use this setting for clean\u2212up operations that shall be executed even when the service failed to start up correctly. Commands configured with this setting need to be able to operate even if the service failed starting up half\u2212way and left incompletely initialized data around. As the service’s processes have been terminated already when the commands specified with this setting are executed they should not attempt to communicate with them.<\/font><\/p>\n

Note that all commands that are configured with this setting are invoked with the result code of the service, as well as the main process’ exit code and status, set in the $SERVICE_RESULT<\/i>, $EXIT_CODE<\/i> and $EXIT_STATUS<\/i> environment variables, see systemd.exec<\/b>(5) for details.<\/font><\/p>\n

Note that the execution of ExecStopPost=<\/i> is taken into account for the purpose of Before=<\/i>\/After=<\/i> ordering constraints.<\/font><\/p>\n

RestartSec=<\/i><\/font><\/p>\n

Configures the time to sleep before restarting a service (as configured with Restart=<\/i>). Takes a unit\u2212less value in seconds, or a time span value such as “5min 20s”. Defaults to 100ms.<\/font><\/p>\n

TimeoutStartSec=<\/i><\/font><\/p>\n

Configures the time to wait for start\u2212up. If a daemon service does not signal start\u2212up completion within the configured time, the service will be considered failed and will be shut down again. The precise action depends on the TimeoutStartFailureMode=<\/i> option. Takes a unit\u2212less value in seconds, or a time span value such as “5min 20s”. Pass “infinity” to disable the timeout logic. Defaults to DefaultTimeoutStartSec=<\/i> from the manager configuration file, except when Type=oneshot<\/i> is used, in which case the timeout is disabled by default (see systemd-system.conf<\/b>(5)).<\/font><\/p>\n

If a service of Type=notify<\/i> sends “EXTEND_TIMEOUT_USEC=…”, this may cause the start time to be extended beyond TimeoutStartSec=<\/i>. The first receipt of this message must occur before TimeoutStartSec=<\/i> is exceeded, and once the start time has extended beyond TimeoutStartSec=<\/i>, the service manager will allow the service to continue to start, provided the service repeats “EXTEND_TIMEOUT_USEC=…” within the interval specified until the service startup status is finished by “READY=1”. (see sd_notify<\/b>(3)).<\/font><\/p>\n

TimeoutStopSec=<\/i><\/font><\/p>\n

This option serves two purposes. First, it configures the time to wait for each ExecStop=<\/i> command. If any of them times out, subsequent ExecStop=<\/i> commands are skipped and the service will be terminated by SIGTERM<\/b>. If no ExecStop=<\/i> commands are specified, the service gets the SIGTERM<\/b> immediately. This default behavior can be changed by the TimeoutStopFailureMode=<\/i> option. Second, it configures the time to wait for the service itself to stop. If it doesn’t terminate in the specified time, it will be forcibly terminated by SIGKILL<\/b> (see KillMode=<\/i> in systemd.kill<\/b>(5)). Takes a unit\u2212less value in seconds, or a time span value such as “5min 20s”. Pass “infinity” to disable the timeout logic. Defaults to DefaultTimeoutStopSec=<\/i> from the manager configuration file (see systemd-system.conf<\/b>(5)).<\/font><\/p>\n

If a service of Type=notify<\/i> sends “EXTEND_TIMEOUT_USEC=…”, this may cause the stop time to be extended beyond TimeoutStopSec=<\/i>. The first receipt of this message must occur before TimeoutStopSec=<\/i> is exceeded, and once the stop time has extended beyond TimeoutStopSec=<\/i>, the service manager will allow the service to continue to stop, provided the service repeats “EXTEND_TIMEOUT_USEC=…” within the interval specified, or terminates itself (see sd_notify<\/b>(3)).<\/font><\/p>\n

TimeoutAbortSec=<\/i><\/font><\/p>\n

This option configures the time to wait for the service to terminate when it was aborted due to a watchdog timeout (see WatchdogSec=<\/i>). If the service has a short TimeoutStopSec=<\/i> this option can be used to give the system more time to write a core dump of the service. Upon expiration the service will be forcibly terminated by SIGKILL<\/b> (see KillMode=<\/i> in systemd.kill<\/b>(5)). The core file will be truncated in this case. Use TimeoutAbortSec=<\/i> to set a sensible timeout for the core dumping per service that is large enough to write all expected data while also being short enough to handle the service failure in due time.<\/font><\/p>\n

Takes a unit\u2212less value in seconds, or a time span value such as “5min 20s”. Pass an empty value to skip the dedicated watchdog abort timeout handling and fall back TimeoutStopSec=<\/i>. Pass “infinity” to disable the timeout logic. Defaults to DefaultTimeoutAbortSec=<\/i> from the manager configuration file (see systemd-system.conf<\/b>(5)).<\/font><\/p>\n

If a service of Type=notify<\/i> handles SIGABRT<\/b> itself (instead of relying on the kernel to write a core dump) it can send “EXTEND_TIMEOUT_USEC=…” to extended the abort time beyond TimeoutAbortSec=<\/i>. The first receipt of this message must occur before TimeoutAbortSec=<\/i> is exceeded, and once the abort time has extended beyond TimeoutAbortSec=<\/i>, the service manager will allow the service to continue to abort, provided the service repeats “EXTEND_TIMEOUT_USEC=…” within the interval specified, or terminates itself (see sd_notify<\/b>(3)).<\/font><\/p>\n

TimeoutSec=<\/i><\/font><\/p>\n

A shorthand for configuring both TimeoutStartSec=<\/i> and TimeoutStopSec=<\/i> to the specified value.<\/font><\/p>\n

TimeoutStartFailureMode=<\/i>, TimeoutStopFailureMode=<\/i><\/font><\/p>\n

These options configure the action that is taken in case a daemon service does not signal start\u2212up within its configured TimeoutStartSec=<\/i>, respectively if it does not stop within TimeoutStopSec=<\/i>. Takes one of terminate<\/b>, abort<\/b> and kill<\/b>. Both options default to terminate<\/b>.<\/font><\/p>\n

If terminate<\/b> is set the service will be gracefully terminated by sending the signal specified in KillSignal=<\/i> (defaults to SIGTERM<\/b>, see systemd.kill<\/b>(5)). If the service does not terminate the FinalKillSignal=<\/i> is sent after TimeoutStopSec=<\/i>. If abort<\/b> is set, WatchdogSignal=<\/i> is sent instead and TimeoutAbortSec=<\/i> applies before sending FinalKillSignal=<\/i>. This setting may be used to analyze services that fail to start\u2212up or shut\u2212down intermittently. By using kill<\/b> the service is immediately terminated by sending FinalKillSignal=<\/i> without any further timeout. This setting can be used to expedite the shutdown of failing services.<\/font><\/p>\n

RuntimeMaxSec=<\/i><\/font><\/p>\n

Configures a maximum time for the service to run. If this is used and the service has been active for longer than the specified time it is terminated and put into a failure state. Note that this setting does not have any effect on Type=oneshot<\/i> services, as they terminate immediately after activation completed. Pass “infinity” (the default) to configure no runtime limit.<\/font><\/p>\n

If a service of Type=notify<\/i> sends “EXTEND_TIMEOUT_USEC=…”, this may cause the runtime to be extended beyond RuntimeMaxSec=<\/i>. The first receipt of this message must occur before RuntimeMaxSec=<\/i> is exceeded, and once the runtime has extended beyond RuntimeMaxSec=<\/i>, the service manager will allow the service to continue to run, provided the service repeats “EXTEND_TIMEOUT_USEC=…” within the interval specified until the service shutdown is achieved by “STOPPING=1” (or termination). (see sd_notify<\/b>(3)).<\/font><\/p>\n

WatchdogSec=<\/i><\/font><\/p>\n

Configures the watchdog timeout for a service. The watchdog is activated when the start\u2212up is completed. The service must call sd_notify<\/b>(3) regularly with “WATCHDOG=1” (i.e. the “keep\u2212alive ping”). If the time between two such calls is larger than the configured time, then the service is placed in a failed state and it will be terminated with SIGABRT<\/b> (or the signal specified by WatchdogSignal=<\/i>). By setting Restart=<\/i> to on\u2212failure<\/b>, on\u2212watchdog<\/b>, on\u2212abnormal<\/b> or always<\/b>, the service will be automatically restarted. The time configured here will be passed to the executed service process in the WATCHDOG_USEC=<\/i> environment variable. This allows daemons to automatically enable the keep\u2212alive pinging logic if watchdog support is enabled for the service. If this option is used, NotifyAccess=<\/i> (see below) should be set to open access to the notification socket provided by systemd. If NotifyAccess=<\/i> is not set, it will be implicitly set to main<\/b>. Defaults to 0, which disables this feature. The service can check whether the service manager expects watchdog keep\u2212alive notifications. See sd_watchdog_enabled<\/b>(3) for details. sd_event_set_watchdog<\/b>(3) may be used to enable automatic watchdog notification support.<\/font><\/p>\n

Restart=<\/i><\/font><\/p>\n

Configures whether the service shall be restarted when the service process exits, is killed, or a timeout is reached. The service process may be the main service process, but it may also be one of the processes specified with ExecStartPre=<\/i>, ExecStartPost=<\/i>, ExecStop=<\/i>, ExecStopPost=<\/i>, or ExecReload=<\/i>. When the death of the process is a result of systemd operation (e.g. service stop or restart), the service will not be restarted. Timeouts include missing the watchdog “keep\u2212alive ping” deadline and a service start, reload, and stop operation timeouts.<\/font><\/p>\n

Takes one of no<\/b>, on\u2212success<\/b>, on\u2212failure<\/b>, on\u2212abnormal<\/b>, on\u2212watchdog<\/b>, on\u2212abort<\/b>, or always<\/b>. If set to no<\/b> (the default), the service will not be restarted. If set to on\u2212success<\/b>, it will be restarted only when the service process exits cleanly. In this context, a clean exit means any of the following:<\/font><\/p>\n

\u2022 exit code of 0;<\/font><\/p>\n

\u2022 for types other than Type=oneshot<\/i>, one of the signals SIGHUP<\/b>, SIGINT<\/b>, SIGTERM<\/b>, or SIGPIPE<\/b>;<\/font><\/p>\n

\u2022 exit statuses and signals specified in SuccessExitStatus=<\/i>.<\/font><\/p>\n

If set to on\u2212failure<\/b>, the service will be restarted when the process exits with a non\u2212zero exit code, is terminated by a signal (including on core dump, but excluding the aforementioned four signals), when an operation (such as service reload) times out, and when the configured watchdog timeout is triggered. If set to on\u2212abnormal<\/b>, the service will be restarted when the process is terminated by a signal (including on core dump, excluding the aforementioned four signals), when an operation times out, or when the watchdog timeout is triggered. If set to on\u2212abort<\/b>, the service will be restarted only if the service process exits due to an uncaught signal not specified as a clean exit status. If set to on\u2212watchdog<\/b>, the service will be restarted only if the watchdog timeout for the service expires. If set to always<\/b>, the service will be restarted regardless of whether it exited cleanly or not, got terminated abnormally by a signal, or hit a timeout.<\/font><\/p>\n

Table\u00a02.\u00a0Exit causes and the effect of the<\/b> Restart=<\/i> settings on them
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/font><\/p>\n

\"Image<\/font><\/p>\n

As exceptions to the setting above, the service will not be restarted if the exit code or signal is specified in RestartPreventExitStatus=<\/i> (see below) or the service is stopped with systemctl stop<\/b> or an equivalent operation. Also, the services will always be restarted if the exit code or signal is specified in RestartForceExitStatus=<\/i> (see below).<\/font><\/p>\n

Note that service restart is subject to unit start rate limiting configured with StartLimitIntervalSec=<\/i> and StartLimitBurst=<\/i>, see systemd.unit<\/b>(5) for details. A restarted service enters the failed state only after the start limits are reached.<\/font><\/p>\n

Setting this to on\u2212failure<\/b> is the recommended choice for long\u2212running services, in order to increase reliability by attempting automatic recovery from errors. For services that shall be able to terminate on their own choice (and avoid immediate restarting), on\u2212abnormal<\/b> is an alternative choice.<\/font><\/p>\n

SuccessExitStatus=<\/i><\/font><\/p>\n

Takes a list of exit status definitions that, when returned by the main service process, will be considered successful termination, in addition to the normal successful exit status 0 and, except for Type=oneshot<\/i>, the signals SIGHUP<\/b>, SIGINT<\/b>, SIGTERM<\/b>, and SIGPIPE<\/b>. Exit status definitions can be numeric termination statuses, termination status names, or termination signal names, separated by spaces. See the Process Exit Codes section in systemd.exec<\/b>(5) for a list of termination status names (for this setting only the part without the “EXIT_” or “EX_” prefix should be used). See signal<\/b>(7) for a list of signal names.<\/font><\/p>\n

Note that this setting does not change the mapping between numeric exit statuses and their names, i.e. regardless how this setting is used 0 will still be mapped to “SUCCESS” (and thus typically shown as “0\/SUCCESS” in tool outputs) and 1 to “FAILURE” (and thus typically shown as “1\/FAILURE”), and so on. It only controls what happens as effect of these exit statuses, and how it propagates to the state of the service as a whole.<\/font><\/p>\n

This option may appear more than once, in which case the list of successful exit statuses is merged. If the empty string is assigned to this option, the list is reset, all prior assignments of this option will have no effect.<\/font><\/p>\n

Example\u00a01.\u00a0A service with the<\/b> SuccessExitStatus=<\/i> setting<\/font><\/p>\n

SuccessExitStatus=TEMPFAIL 250 SIGKILL<\/font><\/p>\n

Exit status 75 (TEMPFAIL<\/b>), 250, and the termination signal SIGKILL<\/b> are considered clean service terminations.<\/font><\/p>\n

Note: systemd\u2212analyze exit\u2212status<\/b> may be used to list exit statuses and translate between numerical status values and names.<\/font><\/p>\n

RestartPreventExitStatus=<\/i><\/font><\/p>\n

Takes a list of exit status definitions that, when returned by the main service process, will prevent automatic service restarts, regardless of the restart setting configured with Restart=<\/i>. Exit status definitions can either be numeric exit codes or termination signal names, and are separated by spaces. Defaults to the empty list, so that, by default, no exit status is excluded from the configured restart logic. For example:<\/font><\/p>\n

RestartPreventExitStatus=1 6 SIGABRT<\/font><\/p>\n

ensures that exit codes 1 and 6 and the termination signal SIGABRT<\/b> will not result in automatic service restarting. This option may appear more than once, in which case the list of restart\u2212preventing statuses is merged. If the empty string is assigned to this option, the list is reset and all prior assignments of this option will have no effect.<\/font><\/p>\n

Note that this setting has no effect on processes configured via ExecStartPre=<\/i>, ExecStartPost=<\/i>, ExecStop=<\/i>, ExecStopPost=<\/i> or ExecReload=<\/i>, but only on the main service process, i.e. either the one invoked by ExecStart=<\/i> or (depending on Type=<\/i>, PIDFile=<\/i>, …) the otherwise configured main process.<\/font><\/p>\n

RestartForceExitStatus=<\/i><\/font><\/p>\n

Takes a list of exit status definitions that, when returned by the main service process, will force automatic service restarts, regardless of the restart setting configured with Restart=<\/i>. The argument format is similar to RestartPreventExitStatus=<\/i>.<\/font><\/p>\n

RootDirectoryStartOnly=<\/i><\/font><\/p>\n

Takes a boolean argument. If true, the root directory, as configured with the RootDirectory=<\/i> option (see systemd.exec<\/b>(5) for more information), is only applied to the process started with ExecStart=<\/i>, and not to the various other ExecStartPre=<\/i>, ExecStartPost=<\/i>, ExecReload=<\/i>, ExecStop=<\/i>, and ExecStopPost=<\/i> commands. If false, the setting is applied to all configured commands the same way. Defaults to false.<\/font><\/p>\n

NonBlocking=<\/i><\/font><\/p>\n

Set the O_NONBLOCK<\/b> flag for all file descriptors passed via socket\u2212based activation. If true, all file descriptors >= 3 (i.e. all except stdin, stdout, stderr), excluding those passed in via the file descriptor storage logic (see FileDescriptorStoreMax=<\/i> for details), will have the O_NONBLOCK<\/b> flag set and hence are in non\u2212blocking mode. This option is only useful in conjunction with a socket unit, as described in systemd.socket<\/b>(5) and has no effect on file descriptors which were previously saved in the file\u2212descriptor store for example. Defaults to false.<\/font><\/p>\n

NotifyAccess=<\/i><\/font><\/p>\n

Controls access to the service status notification socket, as accessible via the sd_notify<\/b>(3) call. Takes one of none<\/b> (the default), main<\/b>, exec<\/b> or all<\/b>. If none<\/b>, no daemon status updates are accepted from the service processes, all status update messages are ignored. If main<\/b>, only service updates sent from the main process of the service are accepted. If exec<\/b>, only service updates sent from any of the main or control processes originating from one of the Exec*=<\/i> commands are accepted. If all<\/b>, all services updates from all members of the service’s control group are accepted. This option should be set to open access to the notification socket when using Type=notify<\/i> or WatchdogSec=<\/i> (see above). If those options are used but NotifyAccess=<\/i> is not configured, it will be implicitly set to main<\/b>.<\/font><\/p>\n

Note that sd_notify()<\/b> notifications may be attributed to units correctly only if either the sending process is still around at the time PID 1 processes the message, or if the sending process is explicitly runtime\u2212tracked by the service manager. The latter is the case if the service manager originally forked off the process, i.e. on all processes that match main<\/b> or exec<\/b>. Conversely, if an auxiliary process of the unit sends an sd_notify()<\/b> message and immediately exits, the service manager might not be able to properly attribute the message to the unit, and thus will ignore it, even if NotifyAccess=<\/i>all<\/b> is set for it.<\/font><\/p>\n

Hence, to eliminate all race conditions involving lookup of the client’s unit and attribution of notifications to units correctly, sd_notify_barrier()<\/b> may be used. This call acts as a synchronization point and ensures all notifications sent before this call have been picked up by the service manager when it returns successfully. Use of sd_notify_barrier()<\/b> is needed for clients which are not invoked by the service manager, otherwise this synchronization mechanism is unnecessary for attribution of notifications to the unit.<\/font><\/p>\n

Sockets=<\/i><\/font><\/p>\n

Specifies the name of the socket units this service shall inherit socket file descriptors from when the service is started. Normally, it should not be necessary to use this setting, as all socket file descriptors whose unit shares the same name as the service (subject to the different unit name suffix of course) are passed to the spawned process.<\/font><\/p>\n

Note that the same socket file descriptors may be passed to multiple processes simultaneously. Also note that a different service may be activated on incoming socket traffic than the one which is ultimately configured to inherit the socket file descriptors. Or, in other words: the Service=<\/i> setting of .socket units does not have to match the inverse of the Sockets=<\/i> setting of the .service it refers to.<\/font><\/p>\n

This option may appear more than once, in which case the list of socket units is merged. Note that once set, clearing the list of sockets again (for example, by assigning the empty string to this option) is not supported.<\/font><\/p>\n

FileDescriptorStoreMax=<\/i><\/font><\/p>\n

Configure how many file descriptors may be stored in the service manager for the service using sd_pid_notify_with_fds<\/b>(3)’s “FDSTORE=1” messages. This is useful for implementing services that can restart after an explicit request or a crash without losing state. Any open sockets and other file descriptors which should not be closed during the restart may be stored this way. Application state can either be serialized to a file in \/run, or better, stored in a memfd_create<\/b>(2) memory file descriptor. Defaults to 0, i.e. no file descriptors may be stored in the service manager. All file descriptors passed to the service manager from a specific service are passed back to the service’s main process on the next service restart (see sd_listen_fds<\/b>(3) for details about the precise protocol used and the order in which the file descriptors are passed). Any file descriptors passed to the service manager are automatically closed when POLLHUP<\/b> or POLLERR<\/b> is seen on them, or when the service is fully stopped and no job is queued or being executed for it. If this option is used, NotifyAccess=<\/i> (see above) should be set to open access to the notification socket provided by systemd. If NotifyAccess=<\/i> is not set, it will be implicitly set to main<\/b>.<\/font><\/p>\n

USBFunctionDescriptors=<\/i><\/font><\/p>\n

Configure the location of a file containing<\/font> USB FunctionFS<\/font><\/b> [2]<\/font><\/small> descriptors, for implementation of USB gadget functions. This is used only in conjunction with a socket unit with ListenUSBFunction=<\/i> configured. The contents of this file are written to the ep0 file after it is opened.<\/font><\/p>\n

USBFunctionStrings=<\/i><\/font><\/p>\n

Configure the location of a file containing USB FunctionFS strings. Behavior is similar to USBFunctionDescriptors=<\/i> above.<\/font><\/p>\n

OOMPolicy=<\/i><\/font><\/p>\n

Configure the Out\u2212Of\u2212Memory (OOM) killer policy. On Linux, when memory becomes scarce the kernel might decide to kill a running process in order to free up memory and reduce memory pressure. This setting takes one of continue<\/b>, stop<\/b> or kill<\/b>. If set to continue<\/b> and a process of the service is killed by the kernel’s OOM killer this is logged but the service continues running. If set to stop<\/b> the event is logged but the service is terminated cleanly by the service manager. If set to kill<\/b> and one of the service’s processes is killed by the OOM killer the kernel is instructed to kill all remaining processes of the service, too. Defaults to the setting DefaultOOMPolicy=<\/i> in systemd-system.conf<\/b>(5) is set to, except for services where Delegate=<\/i> is turned on, where it defaults to continue<\/b>.<\/font><\/p>\n

Use the OOMScoreAdjust=<\/i> setting to configure whether processes of the unit shall be considered preferred or less preferred candidates for process termination by the Linux OOM killer logic. See systemd.exec<\/b>(5) for details.<\/font><\/p>\n

Check systemd.exec<\/b>(5) and systemd.kill<\/b>(5) for more settings.<\/font><\/p>\n

COMMAND LINES <\/a> <\/h2>\n

This section describes command line parsing and variable and specifier substitutions for ExecStart=<\/i>, ExecStartPre=<\/i>, ExecStartPost=<\/i>, ExecReload=<\/i>, ExecStop=<\/i>, and ExecStopPost=<\/i> options.<\/font><\/p>\n

Multiple command lines may be concatenated in a single directive by separating them with semicolons (these semicolons must be passed as separate words). Lone semicolons may be escaped as “;”.<\/font><\/p>\n

Each command line is split on whitespace, with the first item being the command to execute, and the subsequent items being the arguments. Double quotes (“…”) and single quotes (‘…’) may be used to wrap a whole item (the opening quote may appear only at the beginning or after whitespace that is not quoted, and the closing quote must be followed by whitespace or the end of line), in which case everything until the next matching quote becomes part of the same argument. Quotes themselves are removed. C\u2212style escapes are also supported. The table below contains the list of known escape patterns. Only escape patterns which match the syntax in the table are allowed; other patterns may be added in the future and unknown patterns will result in a warning. In particular, any backslashes should be doubled. Finally, a trailing backslash (“”) may be used to merge lines.<\/font><\/p>\n

This syntax is inspired by shell syntax, but only the meta\u2212characters and expansions described in the following paragraphs are understood, and the expansion of variables is different. Specifically, redirection using “<\", \"<<\", \">“, and “>>”, pipes using “|”, running programs in the background using “&”, and other elements of shell syntax are not supported<\/i>.<\/font><\/p>\n

The command to execute may contain spaces, but control characters are not allowed.<\/font><\/p>\n

The command line accepts “%” specifiers as described in systemd.unit<\/b>(5).<\/font><\/p>\n

Basic environment variable substitution is supported. Use “${FOO}” as part of a word, or as a word of its own, on the command line, in which case it will be erased and replaced by the exact value of the environment variable (if any) including all whitespace it contains, always resulting in exactly a single argument. Use “$FOO” as a separate word on the command line, in which case it will be replaced by the value of the environment variable split at whitespace, resulting in zero or more arguments. For this type of expansion, quotes are respected when splitting into words, and afterwards removed.<\/font><\/p>\n

If the command is not a full (absolute) path, it will be resolved to a full path using a fixed search path determinted at compilation time. Searched directories include \/usr\/local\/bin\/, \/usr\/bin\/, \/bin\/ on systems using split \/usr\/bin\/ and \/bin\/ directories, and their sbin\/ counterparts on systems using split bin\/ and sbin\/. It is thus safe to use just the executable name in case of executables located in any of the “standard” directories, and an absolute path must be used in other cases. Using an absolute path is recommended to avoid ambiguity. Hint: this search path may be queried using systemd\u2212path search\u2212binaries\u2212default<\/b>.<\/font><\/p>\n

Example:<\/font><\/p>\n

Environment=”ONE=one” ‘TWO=two two’
ExecStart=echo $ONE $TWO ${TWO}<\/font><\/p>\n

This will execute \/bin\/echo<\/b> with four arguments: “one”, “two”, “two”, and “two two”.<\/font><\/p>\n

Example:<\/font><\/p>\n

Environment=ONE=’one’ “TWO=’two\u00a0two’\u00a0too” THREE=
ExecStart=\/bin\/echo ${ONE} ${TWO} ${THREE}
ExecStart=\/bin\/echo $ONE $TWO $THREE<\/font><\/p>\n

This results in \/bin\/echo being called twice, the first time with arguments “‘one'”, “‘two\u00a0two’\u00a0too”, “”, and the second time with arguments “one”, “two\u00a0two”, “too”.<\/font><\/p>\n

To pass a literal dollar sign, use “$$”. Variables whose value is not known at expansion time are treated as empty strings. Note that the first argument (i.e. the program to execute) may not be a variable.<\/font><\/p>\n

Variables to be used in this fashion may be defined through Environment=<\/i> and EnvironmentFile=<\/i>. In addition, variables listed in the section “Environment variables in spawned processes” in systemd.exec<\/b>(5), which are considered “static configuration”, may be used (this includes e.g. $USER<\/i>, but not $TERM<\/i>).<\/font><\/p>\n

Note that shell command lines are not directly supported. If shell command lines are to be used, they need to be passed explicitly to a shell implementation of some kind. Example:<\/font><\/p>\n

ExecStart=sh \u2212c ‘dmesg | tac’<\/font><\/p>\n

Example:<\/font><\/p>\n

ExecStart=echo one ; echo “two two”<\/font><\/p>\n

This will execute echo<\/b> two times, each time with one argument: “one” and “two two”, respectively. Because two commands are specified, Type=oneshot<\/i> must be used.<\/font><\/p>\n

Example:<\/font><\/p>\n

ExecStart=echo \/ >\/dev\/null & ;
ls<\/font><\/p>\n

This will execute echo<\/b> with five arguments: “\/”, “>\/dev\/null”, “&”, “;”, and “ls”.<\/font><\/p>\n

Table\u00a03.\u00a0C escapes supported in command lines and environment variables<\/b><\/font><\/p>\n

\"Image<\/b><\/font><\/p>\n

EXAMPLES <\/a> <\/h2>\n

Example\u00a02.\u00a0Simple service<\/b><\/font><\/p>\n

The following unit file creates a service that will execute \/usr\/sbin\/foo\u2212daemon. Since no Type=<\/i> is specified, the default Type=<\/i>simple<\/b> will be assumed. systemd will assume the unit to be started immediately after the program has begun executing.<\/font><\/p>\n

[Unit]
Description=Foo<\/font><\/p>\n

[Service]
ExecStart=\/usr\/sbin\/foo\u2212daemon<\/font><\/p>\n

[Install]
WantedBy=multi\u2212user.target<\/font><\/p>\n

Note that systemd assumes here that the process started by systemd will continue running until the service terminates. If the program daemonizes itself (i.e. forks), please use Type=<\/i>forking<\/b> instead.<\/font><\/p>\n

Since no ExecStop=<\/i> was specified, systemd will send SIGTERM to all processes started from this service, and after a timeout also SIGKILL. This behavior can be modified, see systemd.kill<\/b>(5) for details.<\/font><\/p>\n

Note that this unit type does not include any type of notification when a service has completed initialization. For this, you should use other unit types, such as Type=<\/i>notify<\/b> if the service understands systemd’s notification protocol, Type=<\/i>forking<\/b> if the service can background itself or Type=<\/i>dbus<\/b> if the unit acquires a DBus name once initialization is complete. See below.<\/font><\/p>\n

Example\u00a03.\u00a0Oneshot service<\/b><\/font><\/p>\n

Sometimes, units should just execute an action without keeping active processes, such as a filesystem check or a cleanup action on boot. For this, Type=<\/i>oneshot<\/b> exists. Units of this type will wait until the process specified terminates and then fall back to being inactive. The following unit will perform a cleanup action:<\/font><\/p>\n

[Unit]
Description=Cleanup old Foo data<\/font><\/p>\n

[Service]
Type=oneshot
ExecStart=\/usr\/sbin\/foo\u2212cleanup<\/font><\/p>\n

[Install]
WantedBy=multi\u2212user.target<\/font><\/p>\n

Note that systemd will consider the unit to be in the state “starting” until the program has terminated, so ordered dependencies will wait for the program to finish before starting themselves. The unit will revert to the “inactive” state after the execution is done, never reaching the “active” state. That means another request to start the unit will perform the action again.<\/font><\/p>\n

Type=<\/i>oneshot<\/b> are the only service units that may have more than one ExecStart=<\/i> specified. For units with multiple commands (Type=oneshot<\/i>), all commands will be run again.<\/font><\/p>\n

For Type=oneshot<\/i>, Restart=<\/i>always<\/b> and Restart=<\/i>on\u2212success<\/b> are not<\/i> allowed.<\/font><\/p>\n

Example\u00a04.\u00a0Stoppable oneshot service<\/b><\/font><\/p>\n

Similarly to the oneshot services, there are sometimes units that need to execute a program to set up something and then execute another to shut it down, but no process remains active while they are considered “started”. Network configuration can sometimes fall into this category. Another use case is if a oneshot service shall not be executed each time when they are pulled in as a dependency, but only the first time.<\/font><\/p>\n

For this, systemd knows the setting RemainAfterExit=<\/i>yes<\/b>, which causes systemd to consider the unit to be active if the start action exited successfully. This directive can be used with all types, but is most useful with Type=<\/i>oneshot<\/b> and Type=<\/i>simple<\/b>. With Type=<\/i>oneshot<\/b>, systemd waits until the start action has completed before it considers the unit to be active, so dependencies start only after the start action has succeeded. With Type=<\/i>simple<\/b>, dependencies will start immediately after the start action has been dispatched. The following unit provides an example for a simple static firewall.<\/font><\/p>\n

[Unit]
Description=Simple firewall<\/font><\/p>\n

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=\/usr\/local\/sbin\/simple\u2212firewall\u2212start
ExecStop=\/usr\/local\/sbin\/simple\u2212firewall\u2212stop<\/font><\/p>\n

[Install]
WantedBy=multi\u2212user.target<\/font><\/p>\n

Since the unit is considered to be running after the start action has exited, invoking systemctl start<\/b> on that unit again will cause no action to be taken.<\/font><\/p>\n

Example\u00a05.\u00a0Traditional forking services<\/b><\/font><\/p>\n

Many traditional daemons\/services background (i.e. fork, daemonize) themselves when starting. Set Type=<\/i>forking<\/b> in the service’s unit file to support this mode of operation. systemd will consider the service to be in the process of initialization while the original program is still running. Once it exits successfully and at least a process remains (and RemainAfterExit=<\/i>no<\/b>), the service is considered started.<\/font><\/p>\n

Often, a traditional daemon only consists of one process. Therefore, if only one process is left after the original process terminates, systemd will consider that process the main process of the service. In that case, the $MAINPID<\/i> variable will be available in ExecReload=<\/i>, ExecStop=<\/i>, etc.<\/font><\/p>\n

In case more than one process remains, systemd will be unable to determine the main process, so it will not assume there is one. In that case, $MAINPID<\/i> will not expand to anything. However, if the process decides to write a traditional PID file, systemd will be able to read the main PID from there. Please set PIDFile=<\/i> accordingly. Note that the daemon should write that file before finishing with its initialization. Otherwise, systemd might try to read the file before it exists.<\/font><\/p>\n

The following example shows a simple daemon that forks and just starts one process in the background:<\/font><\/p>\n

[Unit]
Description=Some simple daemon<\/font><\/p>\n

[Service]
Type=forking
ExecStart=\/usr\/sbin\/my\u2212simple\u2212daemon \u2212d<\/font><\/p>\n

[Install]
WantedBy=multi\u2212user.target<\/font><\/p>\n

Please see systemd.kill<\/b>(5) for details on how you can influence the way systemd terminates the service.<\/font><\/p>\n

Example\u00a06.\u00a0DBus services<\/b><\/font><\/p>\n

For services that acquire a name on the DBus system bus, use Type=<\/i>dbus<\/b> and set BusName=<\/i> accordingly. The service should not fork (daemonize). systemd will consider the service to be initialized once the name has been acquired on the system bus. The following example shows a typical DBus service:<\/font><\/p>\n

[Unit]
Description=Simple DBus service<\/font><\/p>\n

[Service]
Type=dbus
BusName=org.example.simple\u2212dbus\u2212service
ExecStart=\/usr\/sbin\/simple\u2212dbus\u2212service<\/font><\/p>\n

[Install]
WantedBy=multi\u2212user.target<\/font><\/p>\n

For bus\u2212activatable<\/i> services, do not include a [Install] section in the systemd service file, but use the SystemdService=<\/i> option in the corresponding DBus service file, for example (\/usr\/share\/dbus\u22121\/system\u2212services\/org.example.simple\u2212dbus\u2212service.service):<\/font><\/p>\n

[D\u2212BUS Service]
Name=org.example.simple\u2212dbus\u2212service
Exec=\/usr\/sbin\/simple\u2212dbus\u2212service
User=root
SystemdService=simple\u2212dbus\u2212service.service<\/font><\/p>\n

Please see systemd.kill<\/b>(5) for details on how you can influence the way systemd terminates the service.<\/font><\/p>\n

Example\u00a07.\u00a0Services that notify systemd about their initialization<\/b><\/font><\/p>\n

Type=<\/i>simple<\/b> services are really easy to write, but have the major disadvantage of systemd not being able to tell when initialization of the given service is complete. For this reason, systemd supports a simple notification protocol that allows daemons to make systemd aware that they are done initializing. Use Type=<\/i>notify<\/b> for this. A typical service file for such a daemon would look like this:<\/font><\/p>\n

[Unit]
Description=Simple notifying service<\/font><\/p>\n

[Service]
Type=notify
ExecStart=\/usr\/sbin\/simple\u2212notifying\u2212service<\/font><\/p>\n

[Install]
WantedBy=multi\u2212user.target<\/font><\/p>\n

Note that the daemon has to support systemd’s notification protocol, else systemd will think the service has not started yet and kill it after a timeout. For an example of how to update daemons to support this protocol transparently, take a look at sd_notify<\/b>(3). systemd will consider the unit to be in the ‘starting’ state until a readiness notification has arrived.<\/font><\/p>\n

Please see systemd.kill<\/b>(5) for details on how you can influence the way systemd terminates the service.<\/font><\/p>\n

SEE ALSO <\/a> <\/h2>\n

systemd<\/b>(1), systemctl<\/b>(1), systemd-system.conf<\/b>(5), systemd.unit<\/b>(5), systemd.exec<\/b>(5), systemd.resource-control<\/b>(5), systemd.kill<\/b>(5), systemd.directives<\/b>(7), systemd-run<\/b>(1)<\/font><\/p>\n

NOTES <\/a> <\/h2>\n\n\n
<\/td>\n\n

1.<\/font><\/p>\n<\/td>\n

<\/td>\n\n

Incompatibilities with SysV<\/font><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

https:\/\/www.freedesktop.org\/wiki\/Software\/systemd\/Incompatibilities<\/font><\/p>\n\n\n
<\/td>\n\n

2.<\/font><\/p>\n<\/td>\n

<\/td>\n\n

USB FunctionFS<\/font><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

https:\/\/www.kernel.org\/doc\/Documentation\/usb\/functionfs.txt<\/font><\/p>\n

\n","protected":false},"excerpt":{"rendered":"

systemd.service \u2212 Service unit configuration <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[959],"tags":[961,1291,978],"class_list":["post-4559","post","type-post","status-publish","format-standard","hentry","category-5-formatos-de-ficheros","tag-961","tag-man5","tag-systemd"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4559","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4559"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4559\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4559"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4559"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4559"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}