table of contents
other versions
- jessie 215-17+deb8u7
- jessie-backports 230-7~bpo8+2
- stretch 232-25+deb9u8
- testing 241-1
- stretch-backports 241-1~bpo9+1
- unstable 241-2
SYSTEMD.KILL(5) | systemd.kill | SYSTEMD.KILL(5) |
NAME¶
systemd.kill - Process killing procedure configurationSYNOPSIS¶
service.service, socket.socket, mount.mount, swap.swap, scope.scopeDESCRIPTION¶
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 type. The kill procedure configuration options are configured in the [Service], [Socket], [Mount] or [Swap] section, depending on the unit type.OPTIONS¶
KillMode=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.
KillSignal=
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 to
SIGTERM.
SendSIGHUP=
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".
SendSIGKILL=
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".
SEE ALSO¶
systemd(1), systemctl(1), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5), systemd.exec(5), systemd.directives(7), kill(2), signal(7)systemd 215 |