[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: waiting for process substitutions
From: |
Zachary Santer |
Subject: |
Re: waiting for process substitutions |
Date: |
Wed, 31 Jul 2024 11:48:16 -0400 |
On Fri, Jul 26, 2024 at 10:19 AM Chet Ramey <chet.ramey@case.edu> wrote:
>
> You could have looked at the actual commit, which contains the change log,
> which says
>
> - wait_for_any_job: check for any terminated procsubs as well as any
> terminated background jobs
>
> wait_for_any_job is the function that backs `wait -n' without arguments.
Thanks for the clarification.
$ wait -n > >( cat )
would hang, in the event that there are no other un-waited-for child
processes, right?
> Right now the code that restricts it to the last procsub is commented out.
So you've thought of that?
- Re: waiting for process substitutions, (continued)
- Re: waiting for process substitutions, Zachary Santer, 2024/07/09
- Re: waiting for process substitutions, Zachary Santer, 2024/07/14
- Re: waiting for process substitutions, Chet Ramey, 2024/07/18
- 'wait -n' with and without id arguments, Zachary Santer, 2024/07/20
- Re: 'wait -n' with and without id arguments, Chet Ramey, 2024/07/26
- Re: 'wait -n' with and without id arguments, Zachary Santer, 2024/07/31
- Re: 'wait -n' with and without id arguments, Zachary Santer, 2024/07/31
- Re: waiting for process substitutions, Chet Ramey, 2024/07/18
- Re: waiting for process substitutions, Zachary Santer, 2024/07/20
- Re: waiting for process substitutions, Chet Ramey, 2024/07/26
- Re: waiting for process substitutions,
Zachary Santer <=
- Re: waiting for process substitutions, Chet Ramey, 2024/07/12
- Re: waiting for process substitutions, Robert Elz, 2024/07/12
- Re: waiting for process substitutions, Greg Wooledge, 2024/07/12
- Re: waiting for process substitutions, Oğuz, 2024/07/13