{ "content": [ { "type": "text", "text": "# KILL (man)\n\n## NAME\n\nkill - send a signal to a process\n\n## SYNOPSIS\n\nkill [options] [...]\n\n## DESCRIPTION\n\nThe default signal for kill is TERM. Use -l or -L to list available signals. Particularly\nuseful signals include HUP, INT, KILL, STOP, CONT, and 0. Alternate signals may be specified\nin three ways: -9, -SIGKILL or -KILL. Negative PID values may be used to choose whole\nprocess groups; see the PGID column in ps command output. A PID of -1 is special; it indi‐\ncates all processes except the kill process itself and init.\n\n## TLDR\n\n> Send a signal to a process, usually related to stopping the process.\n\n- Terminate a program using the default SIGTERM (terminate) signal:\n `kill {{process_id}}`\n- List available signal names (to be used without the `SIG` prefix):\n `kill -l`\n- Terminate a program using the SIGHUP (hang up) signal. Many daemons will reload instead of terminating:\n `kill {{-1|-HUP}} {{process_id}}`\n- Terminate a program using the SIGINT (interrupt) signal. This is typically initiated by the user pressing ``:\n `kill {{-2|-INT}} {{process_id}}`\n- Signal the operating system to immediately terminate a program (which gets no chance to capture the signal):\n `kill {{-9|-KILL}} {{process_id}}`\n- Signal the operating system to pause a program until a SIGCONT (\"continue\") signal is received:\n `kill {{-19|-STOP}} {{process_id}}`\n- Send a `SIGUSR1` signal to all processes with the given GID (group id):\n `kill -SIGUSR1 -{{group_id}}`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS** (7 subsections)\n- **EXAMPLES** (4 subsections)\n- **SEE ALSO**\n- **STANDARDS**\n- **AUTHOR**\n- **REPORTING BUGS**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "KILL", "section": "", "mode": "man", "summary": "kill - send a signal to a process", "synopsis": "kill [options] [...]", "tldr_summary": "Send a signal to a process, usually related to stopping the process.", "tldr_examples": [ { "description": "Terminate a program using the default SIGTERM (terminate) signal", "command": "kill {{process_id}}" }, { "description": "List available signal names (to be used without the `SIG` prefix)", "command": "kill -l" }, { "description": "Terminate a program using the SIGHUP (hang up) signal. Many daemons will reload instead of terminating", "command": "kill {{-1|-HUP}} {{process_id}}" }, { "description": "Terminate a program using the SIGINT (interrupt) signal. This is typically initiated by the user pressing ``", "command": "kill {{-2|-INT}} {{process_id}}" }, { "description": "Signal the operating system to immediately terminate a program (which gets no chance to capture the signal)", "command": "kill {{-9|-KILL}} {{process_id}}" }, { "description": "Signal the operating system to pause a program until a SIGCONT (\"continue\") signal is received", "command": "kill {{-19|-STOP}} {{process_id}}" }, { "description": "Send a `SIGUSR1` signal to all processes with the given GID (group id)", "command": "kill -SIGUSR1 -{{group_id}}" } ], "tldr_source": "official", "flags": [ { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "-s", "long": null, "arg": "", "description": "" }, { "flag": "", "long": "--signal", "arg": "", "description": "Specify the signal to be sent. The signal can be specified by using name or number. The behavior of signals is explained in signal(7) manual page." }, { "flag": "-q", "long": "--queue", "arg": null, "description": "Use sigqueue(3) rather than kill(2) and the value argument is used to specify an inte‐ ger to be sent with the signal. If the receiving process has installed a handler for this signal using the SASIGINFO flag to sigaction(2) , then it can obtain this data via the sivalue field of the siginfot structure." }, { "flag": "-l", "long": "--list", "arg": null, "description": "List signal names. This option has optional argument, which will convert signal num‐ ber to signal name, or other way round." }, { "flag": "-L", "long": "--table", "arg": null, "description": "List signal names in a nice table. NOTES Your shell (command line interpreter) may have a built-in kill command. You may need to run the command described here as /bin/kill to solve the conflict." } ], "examples": [ "Kill all processes you can kill.", "Translate number 11 into a signal name.", "List the available signal choices in a nice table.", "Send the default signal, SIGTERM, to all those processes." ], "see_also": [ { "name": "kill", "section": "2", "url": "https://www.chedong.com/phpMan.php/man/kill/2/json" }, { "name": "killall", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/killall/1/json" }, { "name": "nice", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/nice/1/json" }, { "name": "pkill", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/pkill/1/json" }, { "name": "renice", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/renice/1/json" }, { "name": "signal", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/signal/7/json" }, { "name": "sigqueue", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/sigqueue/3/json" }, { "name": "skill", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/skill/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 6, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": " [...]", "lines": 2 }, { "name": "-", "lines": 1 }, { "name": "-s ", "lines": 1, "flag": "-s", "arg": "" }, { "name": "--signal ", "lines": 3, "long": "--signal", "arg": "" }, { "name": "-q --queue", "lines": 5, "flag": "-q", "long": "--queue" }, { "name": "-l --list", "lines": 3, "flag": "-l", "long": "--list" }, { "name": "-L --table", "lines": 6, "flag": "-L", "long": "--table" } ] }, { "name": "EXAMPLES", "lines": 1, "subsections": [ { "name": "kill -9 -1", "lines": 2 }, { "name": "kill -l 11", "lines": 2 }, { "name": "kill -L", "lines": 2 }, { "name": "kill 123 543 2341 3453", "lines": 2 } ] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] }, { "name": "STANDARDS", "lines": 2, "subsections": [] }, { "name": "AUTHOR", "lines": 3, "subsections": [] }, { "name": "REPORTING BUGS", "lines": 5, "subsections": [] } ], "sections": { "NAME": { "content": "kill - send a signal to a process\n", "subsections": [] }, "SYNOPSIS": { "content": "kill [options] [...]\n", "subsections": [] }, "DESCRIPTION": { "content": "The default signal for kill is TERM. Use -l or -L to list available signals. Particularly\nuseful signals include HUP, INT, KILL, STOP, CONT, and 0. Alternate signals may be specified\nin three ways: -9, -SIGKILL or -KILL. Negative PID values may be used to choose whole\nprocess groups; see the PGID column in ps command output. A PID of -1 is special; it indi‐\ncates all processes except the kill process itself and init.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": " [...]", "content": "Send signal to every listed.\n" }, { "name": "-", "content": "" }, { "name": "-s ", "content": "", "flag": "-s", "arg": "" }, { "name": "--signal ", "content": "Specify the signal to be sent. The signal can be specified by using name or number.\nThe behavior of signals is explained in signal(7) manual page.\n", "long": "--signal", "arg": "" }, { "name": "-q --queue", "content": "Use sigqueue(3) rather than kill(2) and the value argument is used to specify an inte‐\nger to be sent with the signal. If the receiving process has installed a handler for\nthis signal using the SASIGINFO flag to sigaction(2) , then it can obtain this data\nvia the sivalue field of the siginfot structure.\n", "flag": "-q", "long": "--queue" }, { "name": "-l --list", "content": "List signal names. This option has optional argument, which will convert signal num‐\nber to signal name, or other way round.\n", "flag": "-l", "long": "--list" }, { "name": "-L --table", "content": "List signal names in a nice table.\n\n\nNOTES Your shell (command line interpreter) may have a built-in kill command. You may need\nto run the command described here as /bin/kill to solve the conflict.\n", "flag": "-L", "long": "--table" } ] }, "EXAMPLES": { "content": "", "subsections": [ { "name": "kill -9 -1", "content": "Kill all processes you can kill.\n" }, { "name": "kill -l 11", "content": "Translate number 11 into a signal name.\n" }, { "name": "kill -L", "content": "List the available signal choices in a nice table.\n" }, { "name": "kill 123 543 2341 3453", "content": "Send the default signal, SIGTERM, to all those processes.\n" } ] }, "SEE ALSO": { "content": "kill(2), killall(1), nice(1), pkill(1), renice(1), signal(7), sigqueue(3), skill(1)\n", "subsections": [] }, "STANDARDS": { "content": "This command meets appropriate standards. The -L flag is Linux-specific.\n", "subsections": [] }, "AUTHOR": { "content": "Albert Cahalan ⟨albert@users.sf.net⟩ wrote kill in 1999 to replace a bsdutils one that was\nnot standards compliant. The util-linux one might also work correctly.\n", "subsections": [] }, "REPORTING BUGS": { "content": "Please send bug reports to ⟨procps@freelists.org⟩\n\n\n\nprocps-ng 2020-04-24 KILL(1)", "subsections": [] } } } }