{
    "content": [
        {
            "type": "text",
            "text": "# systemd.kill (man)\n\n## NAME\n\nsystemd.kill - Process killing procedure configuration\n\n## SYNOPSIS\n\nservice.service, socket.socket, mount.mount, swap.swap, scope.scope\n\n## DESCRIPTION\n\nUnit configuration files for services, sockets, mount points, swap devices and scopes share a\nsubset of configuration options which define the killing procedure of processes belonging to\nthe unit.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS**\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "systemd.kill",
        "section": "",
        "mode": "man",
        "summary": "systemd.kill - Process killing procedure configuration",
        "synopsis": "service.service, socket.socket, mount.mount, swap.swap, scope.scope",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "systemd",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/systemd/1/json"
            },
            {
                "name": "systemctl",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/systemctl/1/json"
            },
            {
                "name": "journalctl",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/journalctl/1/json"
            },
            {
                "name": "systemd.unit",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/systemd.unit/5/json"
            },
            {
                "name": "systemd.service",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/systemd.service/5/json"
            },
            {
                "name": "systemd.socket",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/systemd.socket/5/json"
            },
            {
                "name": "systemd.swap",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/systemd.swap/5/json"
            },
            {
                "name": "systemd.mount",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/systemd.mount/5/json"
            },
            {
                "name": "systemd.exec",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/systemd.exec/5/json"
            },
            {
                "name": "systemd.directives",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/systemd.directives/7/json"
            },
            {
                "name": "kill",
                "section": "2",
                "url": "https://www.chedong.com/phpMan.php/man/kill/2/json"
            },
            {
                "name": "signal",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/signal/7/json"
            },
            {
                "name": "SYSTEMD.KILL",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/SYSTEMD.KILL/5/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 12,
                "subsections": []
            },
            {
                "name": "OPTIONS",
                "lines": 66,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 7,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "systemd.kill - Process killing procedure configuration\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "service.service, socket.socket, mount.mount, swap.swap, scope.scope\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "Unit configuration files for services, sockets, mount points, swap devices and scopes share a\nsubset of configuration options which define the killing procedure of processes belonging to\nthe unit.\n\nThis man page lists the configuration options shared by these five unit types. See\nsystemd.unit(5) for the common options shared by all unit configuration files, and\nsystemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5) and systemd.scope(5)\nfor more information on the configuration file options specific to each unit type.\n\nThe kill procedure configuration options are configured in the [Service], [Socket], [Mount]\nor [Swap] section, depending on the unit type.\n",
                "subsections": []
            },
            "OPTIONS": {
                "content": "KillMode=\nSpecifies how processes of this unit shall be killed. One of control-group, mixed,\nprocess, none.\n\nIf set to control-group, all remaining processes in the control group of this unit will\nbe killed on unit stop (for services: after the stop command is executed, as configured\nwith ExecStop=). If set to mixed, the SIGTERM signal (see below) is sent to the main\nprocess while the subsequent SIGKILL signal (see below) is sent to all remaining\nprocesses of the unit's control group. If set to process, only the main process itself is\nkilled (not recommended!). If set to none, no process is killed (strongly recommended\nagainst!). In this case, only the stop command will be executed on unit stop, but no\nprocess will be killed otherwise. Processes remaining alive after stop are left in their\ncontrol group and the control group continues to exist after stop unless empty.\n\nNote that it is not recommended to set KillMode= to process or even none, as this allows\nprocesses to escape the service manager's lifecycle and resource management, and to\nremain running even while their service is considered stopped and is assumed to not\nconsume any resources.\n\nProcesses will first be terminated via SIGTERM (unless the signal to send is changed via\nKillSignal= or RestartKillSignal=). Optionally, this is immediately followed by a SIGHUP\n(if enabled with SendSIGHUP=). If processes still remain after the main process of a unit\nhas exited or the delay configured via the TimeoutStopSec= has passed, the termination\nrequest is repeated with the SIGKILL signal or the signal specified via FinalKillSignal=\n(unless this is disabled via the SendSIGKILL= option). See kill(2) for more information.\n\nDefaults to control-group.\n\nKillSignal=\nSpecifies which signal to use when stopping a service. This controls the signal that is\nsent as first step of shutting down a unit (see above), and is usually followed by\nSIGKILL (see above and below). For a list of valid signals, see signal(7). Defaults to\nSIGTERM.\n\nNote that, right after sending the signal specified in this setting, systemd will always\nsend SIGCONT, to ensure that even suspended tasks can be terminated cleanly.\n\nRestartKillSignal=\nSpecifies which signal to use when restarting a service. The same as KillSignal=\ndescribed above, with the exception that this setting is used in a restart job. Not set\nby default, and the value of KillSignal= is used.\n\nSendSIGHUP=\nSpecifies whether to send SIGHUP to remaining processes immediately after sending the\nsignal configured with KillSignal=. This is useful to indicate to shells and shell-like\nprograms that their connection has been severed. Takes a boolean value. Defaults to \"no\".\n\nSendSIGKILL=\nSpecifies whether to send SIGKILL (or the signal specified by FinalKillSignal=) to\nremaining processes after a timeout, if the normal shutdown procedure left processes of\nthe service around. When disabled, a KillMode= of control-group or mixed service will not\nrestart if processes from prior services exist within the control group. Takes a boolean\nvalue. Defaults to \"yes\".\n\nFinalKillSignal=\nSpecifies which signal to send to remaining processes after a timeout if SendSIGKILL= is\nenabled. The signal configured here should be one that is not typically caught and\nprocessed by services (SIGTERM is not suitable). Developers can find it useful to use\nthis to generate a coredump to troubleshoot why a service did not terminate upon\nreceiving the initial SIGTERM signal. This can be achieved by configuring LimitCORE= and\nsetting FinalKillSignal= to either SIGQUIT or SIGABRT. Defaults to SIGKILL.\n\nWatchdogSignal=\nSpecifies which signal to use to terminate the service when the watchdog timeout expires\n(enabled through WatchdogSec=). Defaults to SIGABRT.\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "systemd(1), systemctl(1), journalctl(1), systemd.unit(5), systemd.service(5),\nsystemd.socket(5), systemd.swap(5), systemd.mount(5), systemd.exec(5), systemd.directives(7),\nkill(2), signal(7)\n\n\n\nsystemd 249                                                                          SYSTEMD.KILL(5)",
                "subsections": []
            }
        }
    }
}