bash misbehavior

Christopher Faylor me@cgf.cx
Wed Sep 29 03:19:00 GMT 2004


On Tue, Sep 28, 2004 at 11:08:56PM -0400, Pierre A. Humblet wrote:
>Yep, that would work too, but it's costly. In bash there is a new
>process group leader for every command/pipeline
>I will leave this issue simmer for a while.

But does the process group leader always go away?  I would think that
would be a pretty odd case.

>I also tried your patch:
>~: true | `echo true` &
>[1] 616139
>
>But
>~: sleep 1 | `echo true` &
>[2] 621615
>[1]   Done                    true | `echo true`
>~: Use "logout" to leave the shell.
> 
>That was predictable. In bash the first process of a pipeline 
>is the group leader. If it lingers, your patch does not kick in
>and the tcsetpgrp() that shouldn't happen succeeds.
>
>At this point I think it's a bash bug, and I don't see anything
>specific to Cygwin that triggers it !!!
>I will write to the bash maintainer, with cc to this list.

I'll subscribe Chet to the cygwin-developers-allow so that he can subscribe.

cgf



More information about the Cygwin-developers mailing list