On Sat, Oct 12, 2024 at 12:33 PM Oğuz <oguzismailuy...@gmail.com> wrote:
>
> On Saturday, October 12, 2024, Zachary Santer <zsan...@gmail.com> wrote:
>>
>> Backwards compatibility with people's expectations
>
> No one expects children of the same parent to be able to wait for eachother.
> It's common sense.
$ ( set -x; : & wait -- "${sibling_pid}" "${!}" ) > >( cat )${
sibling_pid="${!}"; }
+ :
+ wait -- 7088 7089
bash: wait: pid 7088 is not a child of this shell
${sibling_pid} might be a misnomer there, but hopefully this
illustrates my point that the issues you found were resolved by making
other changes. Even if I try to force 'wait' to wait for everything,
this command won't hang.
On Wed, Aug 7, 2024 at 10:27 AM Chet Ramey <chet.ra...@case.edu> wrote:
>
> It's trivial to do a lot of things that may cause the shell to hang
> besides trying to wait for a process that will never terminate. What
> should the shell do about those?
Thus my question as to the purpose here.
