{
    "mode": "info",
    "parameter": "kill",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/info/kill/json",
    "generated": "2026-07-30T21:44:37Z",
    "sections": {
        "File: coreutils.info,  Node: kill invocation,  Up: Process control": {
            "content": "",
            "subsections": [
                {
                    "name": "24.1 'kill': Send a signal to processes",
                    "content": ""
                }
            ]
        },
        "The 'kill' command sends a signal to processes, causing them to": {
            "content": "terminate or otherwise act upon receiving the signal in some way.\nAlternatively, it lists information about signals.  Synopses:\n\nkill [-s SIGNAL | --signal SIGNAL | -SIGNAL] PID...\nkill [-l | --list | -t | --table] [SIGNAL]...\n\nDue to shell aliases and built-in 'kill' functions, using an\nunadorned 'kill' interactively or in a script may get you different\nfunctionality than that described here.  Invoke it via 'env' (i.e., 'env\nkill ...') to avoid interference from the shell.\n\nThe first form of the 'kill' command sends a signal to all PID\narguments.  The default signal to send if none is specified is 'TERM'.",
            "subsections": []
        },
        "The special signal number '0' does not denote a valid signal, but can be": {
            "content": "used to test whether the PID arguments specify processes to which a\nsignal could be sent.\n\nIf PID is positive, the signal is sent to the process with the\nprocess ID PID.  If PID is zero, the signal is sent to all processes in\nthe process group of the current process.  If PID is -1, the signal is\nsent to all processes for which the user has permission to send a\nsignal.  If PID is less than -1, the signal is sent to all processes in\nthe process group that equals the absolute value of PID.\n\nIf PID is not positive, a system-dependent set of system processes is\nexcluded from the list of processes to which the signal is sent.\n\nIf a negative PID argument is desired as the first one, it should be\npreceded by '--'.  However, as a common extension to POSIX, '--' is not\nrequired with 'kill -SIGNAL -PID'.  The following commands are\nequivalent:\n\nkill -15 -1\nkill -TERM -1\nkill -s TERM -- -1\nkill -- -1\n\nThe first form of the 'kill' command succeeds if every PID argument\nspecifies at least one process that the signal was sent to.\n\nThe second form of the 'kill' command lists signal information.",
            "subsections": []
        },
        "Either the '-l' or '--list' option, or the '-t' or '--table' option must": {
            "content": "be specified.  Without any SIGNAL argument, all supported signals are\nlisted.  The output of '-l' or '--list' is a list of the signal names,\none per line; if SIGNAL is already a name, the signal number is printed\ninstead.  The output of '-t' or '--table' is a table of signal numbers,\nnames, and descriptions.  This form of the 'kill' command succeeds if\nall SIGNAL arguments are valid and if there is no output error.\n\nThe 'kill' command also supports the '--help' and '--version'\noptions.  *Note Common options::.\n\nA SIGNAL may be a signal name like 'HUP', or a signal number like\n'1', or an exit status of a process terminated by the signal.  A signal\nname can be given in canonical form or prefixed by 'SIG'.  The case of\nthe letters is ignored, except for the '-SIGNAL' option which must use\nupper case to avoid ambiguity with lower case option letters.  *Note",
            "subsections": []
        },
        "Signal specifications::, for a list of supported signal names and": {
            "content": "numbers.\n",
            "subsections": []
        }
    },
    "flags": [],
    "examples": [],
    "see_also": []
}