systemd.kill

systemd
Developer Lennart Poettering lennart@poettering.net
systemd.kill 5
systemd.kill Kill environment configuration

`systemd.service`, `systemd.socket`, `systemd.mount`, `systemd.swap`

## Description

Unit configuration files for services, sockets, mount points and swap devices share a subset of configuration options which define the process killing parameters of spawned processes.

This man page lists the configuration options shared by these four unit types. See systemd.unit 5 for the common options of all unit configuration files, and systemd.service 5, systemd.socket 5, systemd.swap 5 and systemd.mount 5 for more information on the specific unit configuration files. The execution specific configuration options are configured in the [Service], [Socket], [Mount] resp. [Swap] section, depending on the unit type.

## Options

`KillMode=`

  Specifies how processes of this service shall be killed. One of `control-group`, `process`, `none`.

  If set to `control-group` all remaining processes in the control group of this unit will be terminated 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 `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. Defaults to `control-group`.

  Processes will first be terminated via SIGTERM (unless the signal to send is changed via `KillSignal=`). If then after a delay (configured via the `TimeoutSec=` 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.

`KillSignal=`

  Specifies which signal to use when killing a service. Defaults to SIGTERM.

`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 8, journalctl 8, systemd.unit 5, systemd.service 5, systemd.socket 5, systemd.swap 5, systemd.mount 5, systemd.exec 5