From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: detect pipe
Date: Sun, 14 Feb 2021 13:20:01 -0800 [thread overview]
Message-ID: <CAH+w=7be-zNuCAqEQYkuzsOukR6_T2R_D2EZTa7F0QPTe=vkHw@mail.gmail.com> (raw)
In-Reply-To: <b5b68acf-8760-5c98-3100-3f1b2d96c69c@eastlink.ca>
On Sun, Feb 14, 2021 at 12:33 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> If it is closed, where does input go? Queued up or vanish?
File descriptors can be shared among processes. Typically for example
the parent shell and any of its children will all have the same
standard input, unless there has been a redirection, including
creating a pipeline.
In the case of a pipeline, if ALL the processes that share a
descriptor have closed it, then the writer of the pipeline will get a
SIGPIPE signal. The "input" (in this case, the output of the process
upstream in the pipeline) is neither queued nor vanishes; the attempt
to write fails and it's up to the writing process to decide how to
react to that, the default being for it to exit.
In the case of a file, the only affected process is the reader, which
gets "invalid file descriptor" if it attempts to read from stdin.
next prev parent reply other threads:[~2021-02-14 21:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 16:45 Ray Andrews
2021-01-27 23:59 ` Bart Schaefer
2021-01-28 4:57 ` Ray Andrews
2021-01-28 6:16 ` Bart Schaefer
2021-01-28 10:08 ` Vincent Lefevre
2021-01-28 10:28 ` Vincent Lefevre
2021-01-28 15:05 ` Ray Andrews
2021-01-28 15:45 ` Ray Andrews
2021-01-28 20:58 ` Bart Schaefer
2021-01-28 20:59 ` Bart Schaefer
2021-01-29 1:17 ` Ray Andrews
2021-01-29 2:50 ` Bart Schaefer
2021-01-29 3:21 ` Ray Andrews
2021-01-30 0:29 ` Bart Schaefer
2021-01-30 14:26 ` Ray Andrews
2021-01-30 19:00 ` Bart Schaefer
2021-01-30 19:19 ` Ray Andrews
2021-01-31 19:12 ` Ray Andrews
2021-01-31 21:28 ` Bart Schaefer
2021-02-14 17:31 ` Vincent Lefevre
2021-02-14 19:33 ` Bart Schaefer
2021-02-14 20:33 ` Ray Andrews
2021-02-14 21:20 ` Bart Schaefer [this message]
2021-02-14 22:25 ` Ray Andrews
2021-02-14 21:24 ` Vincent Lefevre
2021-02-14 21:19 ` Vincent Lefevre
2021-02-14 21:24 ` Bart Schaefer
2021-02-14 21:38 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7be-zNuCAqEQYkuzsOukR6_T2R_D2EZTa7F0QPTe=vkHw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).