Re: bug in bash

[Chet Ramey]

On 5/13/24 3:37 PM, Oğuz wrote:
> On Monday, May 13, 2024, Chet Ramey <chet.ramey@case.edu 
> <mailto:chet.ramey@case.edu>> wrote:
>
>     performs the setpgid in the process forked
>     to run the process substitution).
>
>
> Yes, this sounds like the easy way. I don't know how else to prevent the 
> race in OP. Close stdin/stdout? 

That doesn't change the controlling terminal.

> Direct it from /dev/null?

Same issue.

Setting the process group might solve this particular issue, at the cost of
losing keyboard-generated signals. That's not so bad for SIGINT, though
people do expect to be able to kill a procsub when you interrupt the job
using it, but you also wouldn't be able to suspend the procsub with ^Z any
more. When you're  running a job that contains a process substitution, the
historical behavior has been that you're able to suspend it along with the
rest of the job. Same with hitting the job pgrp with something like SIGHUP.

Chet
--
``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/