[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Multiple concurrent coprocesses
From: |
Alex fxmbsw7 Ratchev |
Subject: |
Re: Multiple concurrent coprocesses |
Date: |
Mon, 22 Mar 2021 16:22:39 +0100 |
i used few coprocs yet didnt have an issue, excepts the 'already
coproc running' warning
i will coproc again, somewhen else
On Mon, Mar 22, 2021 at 2:52 PM Chet Ramey <chet.ramey@case.edu> wrote:
>
> On 3/21/21 4:38 PM, Zachary Santer wrote:
> > Okay. I've at least seen job control report when each coprocess I created
> > on the command line has ended, instead of waiting until they're all dead.
> > And the coproc name going through name expansion is nice. Unless and until
> > I'm allowed to bring my script home, I won't be able to show off what it's
> > able to do, taking advantage of this Bash installation, though.
> >
> > I'm curious what satisfactory testing would look like.
>
> Something more than the trivial cases I've thrown at it. I'm interested in
> whether or not the code has deadlock problems in the presence of pipelines.
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
> ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
>
- Multiple concurrent coprocesses, Zachary Santer, 2021/03/20
- Re: Multiple concurrent coprocesses, Chet Ramey, 2021/03/20
- Re: Multiple concurrent coprocesses, Zachary Santer, 2021/03/21
- Re: Multiple concurrent coprocesses, Chet Ramey, 2021/03/22
- Re: Multiple concurrent coprocesses,
Alex fxmbsw7 Ratchev <=
- Re: Multiple concurrent coprocesses, Zachary Santer, 2021/03/22
- Re: Multiple concurrent coprocesses, Zachary Santer, 2021/03/23
- Re: Multiple concurrent coprocesses, Chet Ramey, 2021/03/30
- Re: Multiple concurrent coprocesses, Zachary Santer, 2021/03/30