Re: Script with set -m launched from interactive shell makes all ancestor shells die

2014-08-15 Thread Chet Ramey
On 8/13/14, 4:40 PM, Chet Ramey wrote: >> Make it executable, and type >> >> ./foo & >> >> at an interactive shell. You get your shell prompt back. You can press >> Enter as many times as you like. But if you press any key other than >> Enter, the entire terminal window goes away. > > I haven'

Re: Script with set -m launched from interactive shell makes all ancestor shells die

2014-08-13 Thread Chet Ramey
On 8/13/14, 12:42 PM, Greg Wooledge wrote: > This was tested on bash 4.3.22 (HP-UX) and bash 4.2.37 (Linux). > > Create a script named foo with the following content: > > #!/bin/bash > set -m > while sleep 1; do :; done > > Make it executable, and type > > ./foo & > > at an interactive shell.

Script with set -m launched from interactive shell makes all ancestor shells die

2014-08-13 Thread Greg Wooledge
This was tested on bash 4.3.22 (HP-UX) and bash 4.2.37 (Linux). Create a script named foo with the following content: #!/bin/bash set -m while sleep 1; do :; done Make it executable, and type ./foo & at an interactive shell. You get your shell prompt back. You can press Enter as many times a