From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: linuxtechguy@gmail.com
Cc: zsh <zsh-users@zsh.org>
Subject: Re: read with redirected stdin
Date: Sun, 8 Jan 2023 05:44:38 +0100 [thread overview]
Message-ID: <CAP+y1xBJ=SJ08efizkY8kkCr2DZeLN1YtdcpyeobcVY1JD5LGg@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6GJo8m1v-v1dwQXddhFDi9q-=Z0o5BsfX6C3-cWCa47e=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Thanks, I'll check it out.
Il giorno dom 8 gen 2023 alle 05:29 Jim <linux.tech.guy@gmail.com> ha
scritto:
>
> On Sat, Jan 7, 2023 at 11:23 AM Pier Paolo Grassi <pierpaolog@gmail.com>
> wrote:
>
>> Thanks, but i don't _always_ redirect stdin.
>> i wonder how is ps getting the tty (it displays an ? when there is no tty
>> for the process)
>> I suppose it uses /proc, but couldn't find a reference or the info
>> exploring the /proc fs by myself.
>> for now I am asking directly ps:
>> [[ "$(ps h -o tty $$)" != "?" ]] && ...
>>
>> Pier Paolo Grassi
>>
>> Hi,
>
> Don't really have an answer how ps gets its info but the attached script
> is something
> I have been working on. It uses the /proc file system directly to get
> info. It uses zstat
> to look for the tty info. If nothing is returned it substitutes '?".
> Some processes point to
> /dev/null. The script is still a work in progress. I was trying to get the
> same results as
> "ps -eHo uid=,pid=,ppid=,tty=,comm=" via a zsh script.
>
> This doesn't answer your original question, but may give you some insight
> into the
> /proc file system.
>
> Hope the script is helpful.
>
> Regards,
>
> Jim Murphy
>
> --
Pier Paolo Grassi
[-- Attachment #2: Type: text/html, Size: 2388 bytes --]
next prev parent reply other threads:[~2023-01-08 4: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 [this message]
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
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='CAP+y1xBJ=SJ08efizkY8kkCr2DZeLN1YtdcpyeobcVY1JD5LGg@mail.gmail.com' \
--to=pierpaolog@gmail.com \
--cc=linuxtechguy@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).