[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wait with trap SIGCHLD: different behaviour in 3.2 and 4.0
From: |
Chet Ramey |
Subject: |
Re: wait with trap SIGCHLD: different behaviour in 3.2 and 4.0 |
Date: |
Thu, 15 Oct 2009 22:02:16 -0400 |
> > 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.
>
> I'll probably make this posix-mode-specific behavior or add an option for
> it in the next version.
Bash-4.1 makes this behavior part of posix mode; the bash-3.2 behavior is
again the default.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: wait with trap SIGCHLD: different behaviour in 3.2 and 4.0,
Chet Ramey <=