Timeline for Link a bash script to the sshd connection that started it, so that we are able to kill it and run another command
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 25, 2019 at 10:55 | review | First posts | |||
| Sep 25, 2019 at 11:06 | |||||
| Sep 24, 2019 at 18:27 | comment | added | ctrl-alt-delor | Out of interest, how did you catch sig-kill (the un-catchable signal). Do you mean sig-term (or another)? | |
| Sep 24, 2019 at 18:25 | history | edited | ctrl-alt-delor | CC BY-SA 4.0 | add comment into question |
| Sep 24, 2019 at 13:53 | answer | added | user147505 | timeline score: 2 | |
| Sep 24, 2019 at 11:07 | comment | added | James Li | how about put the wrapper at server side . If the wrapper find out its parent died , kill its children . notification can be done before cleaning | |
| Sep 23, 2019 at 17:32 | comment | added | ctrl-alt-delor | Have you tried catching HUP? | |
| Sep 23, 2019 at 17:31 | history | edited | ctrl-alt-delor | CC BY-SA 4.0 | fix some of the grammar |
| Sep 23, 2019 at 17:24 | comment | added | Wildcard | What OS? Systemd has features that would help, if you’re on an OS that uses it. | |
| Sep 23, 2019 at 17:17 | history | asked | fmakawa | CC BY-SA 4.0 |