From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page getent.1
Date: Wed, 1 Nov 2023 16:30:10 +0100 [thread overview]
Message-ID: <ZUJvA_RpJtEEqjal@debian> (raw)
In-Reply-To: <ZUJaYg5pUzF_9sP7@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 2928 bytes --]
Hi Helge,
On Wed, Nov 01, 2023 at 02:02:10PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: No "in succession" here on purpose?
I don't understand this report. Please detail.
Thanks,
Alex
P.S.: Please send to <alx@kernel.org>, not to <alx.manpages@gmail.com>,
since I'm deprecating that address.
>
> "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."
>
> "When one I<key> is provided, pass the I<key> to B<setnetgrent>(3) and, "
> "using B<getnetgrent>(3) display the resulting string triple (I<hostname>, "
> "I<username>, I<domainname>). Alternatively, three I<keys> may be provided, "
> "which are interpreted as the I<hostname>, I<username>, and I<domainname> to "
> "match to a netgroup name via B<innetgr>(3). Enumeration is not supported on "
> "B<netgroup>, so either one or three I<keys> must be provided."
>
> "When no I<key> is provided, use B<setnetent>(3), B<getnetent>(3), and "
> "B<endnetent>(3) to enumerate the networks database. When one or more "
> "I<key> arguments are provided, pass each numeric I<key> to "
> "B<getnetbyaddr>(3) and each nonnumeric I<key> to B<getnetbyname>(3) and "
> "display the result."
>
> "When no I<key> is provided, use B<setpwent>(3), B<getpwent>(3), and "
> "B<endpwent>(3) to enumerate the passwd database. When one or more I<key> "
> "arguments are provided, pass each numeric I<key> to B<getpwuid>(3) and each "
> "nonnumeric I<key> to B<getpwnam>(3) and display the result."
>
> "When no I<key> is provided, use B<setprotoent>(3), B<getprotoent>(3), and "
> "B<endprotoent>(3) to enumerate the protocols database. When one or more "
> "I<key> arguments are provided, pass each numeric I<key> to "
> "B<getprotobynumber>(3) and each nonnumeric I<key> to B<getprotobyname>(3) "
> "and display the result."
>
> "When no I<key> is provided, use B<setrpcent>(3), B<getrpcent>(3), and "
> "B<endrpcent>(3) to enumerate the rpc database. When one or more I<key> "
> "arguments are provided, pass each numeric I<key> to B<getrpcbynumber>(3) "
> "and each nonnumeric I<key> to B<getrpcbyname>(3) and display the result."
>
> "When no I<key> is provided, use B<setservent>(3), B<getservent>(3), and "
> "B<endservent>(3) to enumerate the services database. When one or more "
> "I<key> arguments are provided, pass each numeric I<key> to "
> "B<getservbynumber>(3) and each nonnumeric I<key> to B<getservbyname>(3) "
> "and display the result."
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-01 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:02 Issue in man page getent.1 Helge Kreutzmann
2023-11-01 15:30 ` Alejandro Colomar [this message]
2023-11-01 15:44 ` Helge Kreutzmann
2023-11-11 19:49 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 15:38 ` Alejandro Colomar
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 15:28 ` Alejandro Colomar
2024-11-19 13:14 ` Carlos O'Donell
2024-11-19 13:19 ` 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=ZUJvA_RpJtEEqjal@debian \
--to=alx@kernel.org \
--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