Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16668
| From | Ángel <angel@16bits.net> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Issue with Bash |
| Date | 2020-08-01 01:27 +0200 |
| Message-ID | <mailman.413.1596238078.2739.bug-bash@gnu.org> (permalink) |
| References | (5 earlier) <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> <5f08f49d-e8d3-fe63-d9f5-27bea4e78e55@case.edu> <1596238069.1058.29.camel@16bits.net> |
On 2020-07-31 at 10:13 -0400, Chet Ramey wrote: > > 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
Back to gnu.bash.bug | Previous | Next | Find similar
Re: Issue with Bash Ángel <angel@16bits.net> - 2020-08-01 01:27 +0200
csiph-web