Timeline for What does kill 0 do actually? [closed]
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 3, 2017 at 18:46 | review | Reopen votes | |||
| Dec 3, 2017 at 21:17 | |||||
| Jan 5, 2017 at 15:15 | history | closed | countermode Kusalananda♦ Eric Renouf grochmal Rui F Ribeiro | Not suitable for this site | |
| Jan 5, 2017 at 6:00 | vote | accept | Firegun | ||
| Jan 4, 2017 at 23:01 | review | Close votes | |||
| Jan 5, 2017 at 15:15 | |||||
| Jan 4, 2017 at 22:55 | comment | added | Adam Katz | This question is actually a copy of SuperUser question What does kill 0 do actually? (which was migrated from StackOverflow). See also questions about kill -0 (note the dash), which is a different topic, at StackOverflow and here on Unix.SE. | |
| Mar 22, 2013 at 22:54 | history | edited | Gilles 'SO- stop being evil' | edited tags | |
| Mar 11, 2013 at 11:06 | answer | added | Stéphane Chazelas | timeline score: 35 | |
| Mar 11, 2013 at 8:54 | comment | added | Stéphane Chazelas | @jordanm, no. a job started by an interactive shell has a different process group than the shell. That's how the shell can put it in foreground and background. See ps -j to see the process groups. | |
| Mar 11, 2013 at 5:48 | comment | added | jordanm | It sends a SIGTERM to the process, which it has done. The man command has chosen to ignore it. | |
| Mar 11, 2013 at 5:05 | history | asked | Firegun | CC BY-SA 3.0 |