Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Helge Kreutzmann <debian@helgefjell.de>,
	mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page getent.1
Date: Tue, 19 Nov 2024 14:19:37 +0100	[thread overview]
Message-ID: <20241119131937.bv5xrxw3o4j32uxn@devuan> (raw)
In-Reply-To: <4b802b9f-dc7a-49c1-a363-7ac987c82474@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]

Hi Carlos,

On Tue, Nov 19, 2024 at 08:14:48AM -0500, Carlos O'Donell wrote:
> On 11/17/24 5:46 AM, Helge Kreutzmann wrote:
> > Without further ado, the following was found:
> > 
> > Issue:    No "in succession" here on purpose?
> > 
> > "When no I<key> is provided, use B<sethostent>(3), B<gethostent>(3), and "
> > "B<endhostent>(3)  to enumerate the hosts database.  When one or more I<key> "
> > "arguments are provided, pass each I<key> to B<gethostbyaddr>(3)  or "
> > "B<gethostbyname2>(3), depending on whether a call to B<inet_pton>(3)  "
> > "indicates that the I<key> is an IPv6 or IPv4 address or not, and display the "
> > "result."
> 
> This text is for the "hosts" database.
> 
> > … and in many other paragraphs (I can provide you the full list). Last
> > time you said, that this is under review with glibc - are there any
> > results on this?
> 
> As an upstream glibc maintainer I can comment on this.
> 
> The getent program today iterates over the keys passing them in succession to the calls
> as listed for the "hosts" database i.e. nss/getent.c:hosts_keys.
> 
> I think the text could be improved by making it consistent for "hosts."

Thanks!

> 
> Each one of these instances is different so they each should be enumerated and reviewed
> separately.

Would you mind proposing some patches?

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-11-19 13:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-17 10:46 Issue in man page getent.1 Helge Kreutzmann
2024-11-17 15:28 ` Alejandro Colomar
2024-11-19 13:14 ` Carlos O'Donell
2024-11-19 13:19   ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 15:38 ` Alejandro Colomar
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 15:30 ` Alejandro Colomar
2023-11-01 15:44   ` Helge Kreutzmann
2023-11-11 19:49     ` Alejandro Colomar

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=20241119131937.bv5xrxw3o4j32uxn@devuan \
    --to=alx@kernel.org \
    --cc=carlos@redhat.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    /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