SIGHUP is a signal caught between two worlds. It was born from the physical "hang up" of terminal lines, and its original meaning—the loss of a controlling terminal—still applies.
Hi @FUNC25
Thank you for a great post.
Just wanted to clarify that
> By default, the shell forwards the SIGHUP signal to all its child processes.
is true only for interactive shells, according to [1], so scripted shells will not inherit this behavior.
[1] - https://www.gnu.org/software/bash/manual/html_node/Signals.html#:~:text=Before%20exiting%2C%20an%20interactive%20shell%20resends%20the%20SIGHUP%20to%20all%20jobs%2C%20running%20or%20stopped
Thanks, see my reply at https://substack.com/profile/162049535-phuong-le/note/c-111933966.
Hi @FUNC25
Thank you for a great post.
Just wanted to clarify that
> By default, the shell forwards the SIGHUP signal to all its child processes.
is true only for interactive shells, according to [1], so scripted shells will not inherit this behavior.
[1] - https://www.gnu.org/software/bash/manual/html_node/Signals.html#:~:text=Before%20exiting%2C%20an%20interactive%20shell%20resends%20the%20SIGHUP%20to%20all%20jobs%2C%20running%20or%20stopped
Thanks, see my reply at https://substack.com/profile/162049535-phuong-le/note/c-111933966.