Re: kill the LHS command of a pipe once the RHS command terminates

[Vincent Lefevre <vincent@xxxxxxxxxx>]

On 2019-07-29 17:00:30 -0700, Bart Schaefer wrote:
> On Mon, Jul 29, 2019 at 1:50 PM Vincent Lefevre <vincent@xxxxxxxxxx> wrote:
> >
> > > > Concerning the documentation, the zshexpn(1) man page does not say
> > > > that a process in process substitution is run in background.
> > >
> > > They have to be, otherwise either you'd need unlimited buffering or
> > > the read of the descriptor could deadlock.
> >
> > I don't see how this is related to buffering. This would be the same
> > case as with a pipe (cmd1 | cmd2), for which both commands run in
> > foreground and there are no buffering issues.
> 
> You're wrong about this.  In (cmd1 | cmd2), zsh forks off cmd1 into
> its own process.  It is effectively "in the background" even though
> the entire pipeline is considered to be in the foreground; the only
> process that is really "in the foreground" is cmd2.

No, cmd1 is definitely not run in background, as ssh (as a descendent
of cmd1) still has access to the controlling terminal: I can type the
passphrase, which was not the case with <() process substitution.

> > It says that jobs explicitly put into the background are run
> > asynchronously, but nothing about the converse.
> 
> I'm not sure how you get "nothing about the converse" from "Certain
> jobs are run asynchronously  ... OTHER THAN THOSE explicitly put into
> the background;" ("other than" refers to "certain jobs" that are
> asynchronous but "(not) explicitly" backgrounded) and "Examples of
> such asynchronous jobs are process  substitution" ... but in any case

I meant that zsh does not say whether jobs that are run asynchronously
are necessarily background processes (thus with no access to the
controlling terminal).

> this was one of those cases where the zsh manual assumed you know how
> "most" shells work and therefore what these terms mean, and that it
> only had to explain what it might be doing differently.  The whole
> manual page used to be written this way and we are only gradually
> turning it into a standalone reference.

The reference is POSIX, and POSIX does not seem to use the notion of
"run asynchronously" as in zsh. There are "asynchronous lists", but
these are exclusively commands terminated by "&".

-- 
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)