On 9/17/25 11:09 AM, pourko--- via Bug reports for the GNU Bourne Again
SHell wrote:
Chet Ramey wrote:
It's more likely that the OP is running the scripts from an interactive
shell that is not bash.
On my box I have no shells other than bash, and even sh is symlinked to bash
~# help | head -1
GNU bash, version 5.2.37(47)-release (x86_64-slackware-linux-gnu)
The behavior you're reporting with your `corrected' script is not what
other people using an interactive bash instance to run the `t1' script
see. That includes me.
Everyone gets a message about `t1' being stopped, so it must be something
else. Even if you didn't have job control enabled for some reason, you
would not get this result, since asynchronous commands get /dev/null as
their standard input when job control is not active.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/
