> > Cool. Is there any hint/doc/faq/how-to implement old behaviour, i.e. wait
> > until all children of current bash process will exit?
>
> I imagine a loop on wait until it returns because there are no unwaited-for
> children. You can detect the "interrupted" exit status and behave
> accordingly
Hi!
On Sun, Sep 27, 2009 at 11:06:43PM -0400, Chet Ramey wrote:
> > Description:
> > Looks like 'wait' command in bash-4 is broken: if used together
> > with 'trap myhandler SIGCHLD' the 'wait' (without params) exit
> > just after receiving first child exit, instead of wait
> > This was reported as a bug against bash-3.2.
>
> Cool. Is there any hint/doc/faq/how-to implement old behaviour, i.e. wait
> until all children of current bash process will exit?
I imagine a loop on wait until it returns because there are no unwaited-for
children. You can detect the "interru
power...@powerman.name wrote:
> Bash Version: 4.0
> Patch Level: 28
> Release Status: release
>
> Description:
> Looks like 'wait' command in bash-4 is broken: if used together
> with 'trap myhandler SIGCHLD' the 'wait' (without params) exit
> just after receiving first ch
