From: Bart Schaefer <schaefer@brasslantern.com>
To: linuxtechguy@gmail.com
Cc: Pier Paolo Grassi <pierpaolog@gmail.com>, zsh <zsh-users@zsh.org>
Subject: Re: read with redirected stdin
Date: Mon, 9 Jan 2023 18:46:31 -0800 [thread overview]
Message-ID: <CAH+w=7ZpTnYYZD7yzKr-5pk97Lao1prVSF5UDP7P=Lxd+zkmvA@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6G+u0ePsa2Y_rUqzHsVHsk9SG=we334xa-PHgX1EREL8Mw@mail.gmail.com>
On Mon, Jan 9, 2023 at 2:47 PM Jim <linux.tech.guy@gmail.com> wrote:
>
> I haven't seen anything that shows ttys pointing to a process. It may exist, but I don't
> know where you would find it if it does. I just know that processes attach tty devices
> via file descriptors on Linux and Unix systems.
Although the foregoing is correct, once a process is attached to a tty
the corresponding descriptor can be closed or duplicated without
detaching the process from the tty again. All descendants of that
process form a "process group" (unless one of them explicitly takes
over as a new "group leader") and all processes in a group are
eligible to receive signals such as INT and QUIT and TSTP generated by
the terminal (usually by keyboard interaction).
So Pier wants to know what tty is associated with the current
process's group, not what tty may be performing i/o with any of the
currently open descriptors. The simplest way to do that is to use the
coreutils "tty" command: tty < /dev/tty
next prev parent reply other threads:[~2023-01-10 2:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 13:31 Pier Paolo Grassi
2023-01-07 13:44 ` Roman Perepelitsa
2023-01-07 17:21 ` Pier Paolo Grassi
2023-01-07 17:31 ` Roman Perepelitsa
2023-01-07 17:36 ` Pier Paolo Grassi
2023-01-07 17:52 ` Roman Perepelitsa
2023-01-08 13:23 ` Daniel Shahaf
2023-01-08 13:48 ` Roman Perepelitsa
2023-01-08 14:21 ` Daniel Shahaf
2023-01-08 14:42 ` Roman Perepelitsa
2023-01-07 17:33 ` Pier Paolo Grassi
2023-01-08 4:28 ` Jim
2023-01-08 4:44 ` Pier Paolo Grassi
2023-01-08 21:18 ` Jim
2023-01-09 16:01 ` Pier Paolo Grassi
2023-01-09 22:47 ` Jim
2023-01-10 2:46 ` Bart Schaefer [this message]
2023-01-10 6:03 ` Pier Paolo Grassi
2023-01-08 14:44 ` Ray Andrews
2023-01-08 15:06 ` Roman Perepelitsa
2023-01-08 20:23 ` Ray Andrews
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=7ZpTnYYZD7yzKr-5pk97Lao1prVSF5UDP7P=Lxd+zkmvA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=linuxtechguy@gmail.com \
--cc=pierpaolog@gmail.com \
--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).