Unit configuration files for services, sockets, mount points, swap
devices and scopes share a subset of configuration options which
define the killing procedure of processes belonging to the unit.
This man page lists the configuration options shared by these five
unit types. See systemd.unit(5) for the common options shared by all
unit configuration files, and systemd.service(5), systemd.socket(5),
systemd.swap(5), systemd.mount(5) and systemd.scope(5) for more
information on the configuration file options specific to each unit
The kill procedure configuration options are configured in the
[Service], [Socket], [Mount] or [Swap] section, depending on the unit
Specifies how processes of this unit shall be killed. One of
control-group, process, mixed, none.
If set to control-group, all remaining processes in the control
group of this unit will be killed on unit stop (for services:
after the stop command is executed, as configured with
ExecStop=). If set to process, only the main process itself is
killed. If set to mixed, the SIGTERM signal (see below) is sent
to the main process while the subsequent SIGKILL signal (see
below) is sent to all remaining processes of the unit's control
group. If set to none, no process is killed. In this case, only
the stop command will be executed on unit stop, but no process be
killed otherwise. Processes remaining alive after stop are left
in their control group and the control group continues to exist
after stop unless it is empty.
Processes will first be terminated via SIGTERM (unless the signal
to send is changed via KillSignal=). Optionally, this is
immediately followed by a SIGHUP (if enabled with SendSIGHUP=).
If then, after a delay (configured via the TimeoutStopSec=
option), processes still remain, the termination request is
repeated with the SIGKILL signal (unless this is disabled via the
SendSIGKILL= option). See kill(2) for more information.
Defaults to control-group.
Specifies which signal to use when killing a service. This
controls the signal that is sent as first step of shutting down a
unit (see above), and is usually followed by SIGKILL (see above
and below). For a list of valid signals, see signal(7). Defaults
Note that, right after sending the signal specified in this
setting, systemd will always send SIGCONT, to ensure that even
suspended tasks can be terminated cleanly.
Specifies whether to send SIGHUP to remaining processes
immediately after sending the signal configured with KillSignal=.
This is useful to indicate to shells and shell-like programs that
their connection has been severed. Takes a boolean value.
Defaults to "no".
Specifies whether to send SIGKILL to remaining processes after a
timeout, if the normal shutdown procedure left processes of the
service around. Takes a boolean value. Defaults to "yes".
This page is part of the systemd (systemd system and service manager)
project. Information about the project can be found at
⟨http://www.freedesktop.org/wiki/Software/systemd⟩. If you have a bug
report for this manual page, see
page was obtained from the project's upstream Git repository
⟨https://github.com/systemd/systemd.git⟩ on 2017-03-13. If you dis‐
cover any rendering problems in this HTML version of the page, or you
believe there is a better or more up-to-date source for the page, or
you have corrections or improvements to the information in this
COLOPHON (which is not part of the original manual page), send a mail
systemd 233 SYSTEMD.KILL(5)