Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: =?ISO-8859-1?Q?=C1ngel?= Newsgroups: gnu.bash.bug Subject: Re: Issue with Bash Date: Sat, 01 Aug 2020 01:27:49 +0200 Lines: 15 Approved: bug-bash@gnu.org Message-ID: References: <76d97603-ac8b-1952-cb10-f178fd8989db@case.edu> <5f08f49d-e8d3-fe63-d9f5-27bea4e78e55@case.edu> <1596238069.1058.29.camel@16bits.net> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable X-Trace: usenet.stanford.edu 1596238079 31236 209.51.188.17 (31 Jul 2020 23:27:59 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org In-Reply-To: <5f08f49d-e8d3-fe63-d9f5-27bea4e78e55@case.edu> Received-SPF: pass client-ip=199.195.249.9; envelope-from=angel@16bits.net; helo=mailer.hiddenmail.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/07/31 19:15:34 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <1596238069.1058.29.camel@16bits.net> X-Mailman-Original-References: <76d97603-ac8b-1952-cb10-f178fd8989db@case.edu> <5f08f49d-e8d3-fe63-d9f5-27bea4e78e55@case.edu> Xref: csiph.com gnu.bash.bug:16668 On 2020-07-31 at 10:13 -0400, Chet Ramey wrote: >=20 > I'm going to have to test some more. When I tried it, all the shells > died. > (I did send the SIGHUP from another terminal.) I was using ksh93 as > the parent and bash-5.0.18 as the interactive bash, running on macOS. This is probably AIX-specific in that some ioctl called by tcsetattr seems to cause a SIGHUP when there is no tty. Their behavior kinda make sense. Can probably be easily fixed by masking SIGHUP in the handler. Cheers