Timeline for Difference between closing terminal and closing shell on child processes
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 18, 2018 at 10:57 | comment | added | JdeBP | It's not dependent from the terminal emulator, it's not a mess, and it's not Linux-specific; although it does vary by shell. This is long-standardized behaviour and we already have lots of questions on it for people to read, starting with: unix.stackexchange.com/questions/407448 , unix.stackexchange.com/questions/446250 , unix.stackexchange.com/questions/84737 , unix.stackexchange.com/questions/158727 , unix.stackexchange.com/questions/162749 , … | |
| Oct 18, 2018 at 8:59 | comment | added | xenoid | When you close the terminal the processes receive a SIGHUP (which is why there is a nohup command...) | |
| Oct 18, 2018 at 7:23 | comment | added | 炸鱼薯条德里克 | Every time I see such questions, I started to blame the Linux kernel, the job control system relying on the concept of control terminal and signals are a total mess. When shell exit, the kernel just changes PPID, but the shell itself might want to send some signals to children or processes in its process group indicating "I'm dying, take care!". When the terminal emulator process dies, it might do the same or different things. | |
| Oct 18, 2018 at 6:50 | history | edited | bob dylan | CC BY-SA 4.0 | added 1 character in body |
| S Oct 18, 2018 at 6:43 | history | suggested | Gonçalo Peres | Improve tags | |
| Oct 18, 2018 at 6:43 | review | Suggested edits | |||
| S Oct 18, 2018 at 6:43 | |||||
| Oct 18, 2018 at 6:35 | history | edited | bob dylan | CC BY-SA 4.0 | added 2 characters in body |
| Oct 18, 2018 at 6:24 | history | asked | bob dylan | CC BY-SA 4.0 |