Re: Change in SIGTERM behaviour in bash 4.3 when using readline

From	Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups	gnu.bash.bug
Subject	Re: Change in SIGTERM behaviour in bash 4.3 when using readline
Date	2020-03-04 15:51 -0500
Message-ID	<mailman.2052.1583355091.2412.bug-bash@gnu.org> (permalink)
References	<20200304181824.GA394387@chrisdown.name> <20200304192918.GB394387@chrisdown.name> <20200304193834.GC394387@chrisdown.name> <564361ee-9f98-adca-ccfe-97c8ed11ff2a@case.edu> <20200304205100.GT845@eeg.ccf.org>

Show all headers | View raw

On Wed, Mar 04, 2020 at 03:43:26PM -0500, Chet Ramey wrote:
> On 3/4/20 2:38 PM, Chris Down wrote:
> > --- a/jobs.c
> > +++ b/jobs.c
> > @@ -4584,6 +4584,7 @@ initialize_job_signals ()
> >    if (interactive)
> >      {
> >        set_signal_handler (SIGINT, sigint_sighandler);
> > +      set_signal_handler (SIGTERM, SIG_IGN);
> 
> This is how the code used to read, before I added the do-nothing signal
> handler as a result of
> 
> https://lists.gnu.org/archive/html/bug-bash/2013-02/msg00020.html

The man page might need an update as well.

SIGNALS
       When bash is interactive, in the  absence  of  any  traps,  it  ignores
       SIGTERM (so that kill 0 does not kill an interactive shell) [...]

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Change in SIGTERM behaviour in bash 4.3 when using readline Greg Wooledge <wooledg@eeg.ccf.org> - 2020-03-04 15:51 -0500

csiph-web