Re: Issue with Bash

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Issue with Bash
Date	2020-08-02 17:42 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.602.1596404548.2739.bug-bash@gnu.org> (permalink)
References	(4 earlier) <OFDCE7FFF8.B623ABC2-ON002585AB.0023ACB2-002585AB.0023F29F@notes.na.collabserv.com> <OFBE0423CD.27BCE8FB-ON002585B6.00241358-002585B6.0028D3D0@notes.na.collabserv.com> <76d97603-ac8b-1952-cb10-f178fd8989db@case.edu> <OF45ED3104.7A08B8C2-ON002585B6.004C26CF-652585B6.004D45B3@notes.na.collabserv.com> <e5f58a30-61df-4880-0fa3-a9cb6e8da995@case.edu>

Show all headers | View raw

On 7/31/20 10:04 AM, Ayappan P2 wrote:
> We are passing SIGHUP from another terminal ( not from the terminal which
> has the interactive bash shell) . The terminal which has the interactive
> bash closes immediately.
> 
> The scenario is we just open two terminals. In one terminal , just invoke
> bash . And from another terminal pass SIGHUP to the parent process (ksh) of
> bash.

That part is all fine, it's the fact that bash gets SIGHUP when it calls
tcsetattr(), when SIGHUP isn't one of the signals that is documented as
valid for tcsetattr().

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

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

Thread

Re: Issue with Bash Chet Ramey <chet.ramey@case.edu> - 2020-08-02 17:42 -0400

csiph-web