Timeline for What is the `-KILL` option in `pkill` command
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S May 3, 2022 at 16:14 | history | suggested | Manuel Jordan | CC BY-SA 4.0 | Improve presentation and fix minor typos |
| May 3, 2022 at 14:46 | review | Suggested edits | |||
| S May 3, 2022 at 16:14 | |||||
| Jan 31, 2018 at 18:37 | history | edited | DopeGhoti | CC BY-SA 3.0 | Add info about SIGUP |
| Jan 31, 2018 at 17:40 | comment | added | JdeBP | If the goal is logging out users, then really a SIGHUP should be sent before sending either of those. | |
| Jan 31, 2018 at 17:15 | comment | added | DopeGhoti | While it is true that SIGTERM is the default, I prefer to explicitly state which signal I wish to send when using KILL as a self-imposed sanity check. It also makes editing the command line / script to send non-TERM signals easier on later iterations if needed. | |
| Jan 31, 2018 at 16:51 | comment | added | quixotic | note kill and pkill will send SIGTERM by default. try pkill foo before sending pkill -KILL foo. | |
| Jan 31, 2018 at 16:46 | vote | accept | Tower | ||
| Jan 31, 2018 at 16:31 | comment | added | Stéphane Chazelas | Note that SIGTERM is not handled by commands by default. The stdio buffers for instance are not flushed by default upon SIGTERM. The commands will have to actively install a handler on SIGTERM for that. On GNU/Linux systems see ps -eo caught,pid,args | gawk -v t="$(kill -l TERM)" 'and(strtonum("0x"$1), 2**(t-1))' for a list of processes that do have a handler on SIGTERM. | |
| Jan 31, 2018 at 16:18 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 | added 67 characters in body |
| Jan 31, 2018 at 16:13 | history | answered | DopeGhoti | CC BY-SA 3.0 |