From: Jordi Sanfeliu <jordi@fibranet.cat>
To: newlib@sourceware.org
Subject: Re: [PATCH] Fix getlogin() to check only stdin to get a valid tty
Date: Thu, 13 Jul 2023 10:06:58 +0200 [thread overview]
Message-ID: <d9e4c327-e623-2a5b-6910-9dfaaea1b7c6@fibranet.cat> (raw)
In-Reply-To: <74633613-8420-5ad6-2882-6ad14066f781@foss.st.com>
Hello Torbjörn,
Thanks for you reply.
It seems to me that this code returns 0 as soon as one of the 3 fds is
0, regardless if the rest are valid tty names.
I think that what you meant is this:
if ((tty = ttyname (0)) == 0)
if ((tty = ttyname (1)) == 0)
if ((tty = ttyname (2)) == 0)
return 0;
which IMO would be even a better patch.
What do you think?
Best regards.
On 7/12/23 20:50, Torbjorn SVENSSON wrote:
>> - if (((tty = ttyname (0)) == 0)
>> - || ((tty = ttyname (1)) == 0)
>> - || ((tty = ttyname (2)) == 0))
>
> These 3 lines of code checks if one of stdin, stdout or stderr is
> connected to a terminal device. If the return value of ttyname is 0, it
> means that there is no terminal device connected to that fd.
> As I read the code, it first tries with stdin. If stdin is closed or
> redirected, it tries with stdout instead and then lastly, falls back to
> trying with stderr. If none of the 3 fd's provides a terminal device,
> then the getlogin will return 0.
--
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat
next prev parent reply other threads:[~2023-07-13 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 17:33 Jordi Sanfeliu
2023-07-12 18:50 ` Torbjorn SVENSSON
2023-07-12 20:06 ` Brian Inglis
2023-07-13 16:26 ` Torbjorn SVENSSON
2023-07-13 8:06 ` Jordi Sanfeliu [this message]
2023-07-13 16:25 ` Torbjorn SVENSSON
2023-07-13 16:57 ` Jordi Sanfeliu
2023-07-13 19:01 ` Jeff Johnston
2023-07-17 7:54 ` Corinna Vinschen
2023-07-13 21:12 ` Stefan Tauner
2023-07-17 19:06 ` Jeff Johnston
2023-07-18 5:57 ` Jordi Sanfeliu
2023-07-18 7:08 ` Jordi Sanfeliu
2023-07-18 17:44 ` Jeff Johnston
2023-07-18 18:59 ` Jordi Sanfeliu
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=d9e4c327-e623-2a5b-6910-9dfaaea1b7c6@fibranet.cat \
--to=jordi@fibranet.cat \
--cc=newlib@sourceware.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).