On Mon, Oct 12, 2026 at 4:09 PM Chet Ramey <chet.ramey@case.edu
<mailto:chet.ramey@case.edu>> wrote:
On 10/11/26 10:33 AM, Denys Vlasenko via Bug reports for the GNU Bourne
Again SHell wrote:
> Now the same but with SIGTERM:
>
> me@myhost>$ bash
> me@myhost>$ export PS1='Prompt> '; trap 'echo T' term; (while kill $
$; do
> sleep 1; done) &
> [1] 65964
> Prompt>
> exit
> me@myhost>$ bash: line 1: kill: (65904) - No such process
>
> without me pressing anything. Why did bash exit?! The trap does not
contain
> any 'exit' commands!
Readline treats SIGTERM as a fatal signal, like SIGHUP. This allows it to
exit the calling application if, for instance, the terminal emulator
window in which it's running is closed.
Well, SIGTERM has nothing to do with tty's closure, why does it
do that *on SIGTERM*?