From: Simon Essien <champbreed1@gmail.com>
To: alex@manpages.org, linux-man@vger.kernel.org
Cc: Simon Essien <champbreed1@gmail.com>
Subject: [PATCH v2 2/2] man3/getgrnam: clarify error behavior when entry is not found
Date: Thu, 27 Nov 2025 13:22:32 +0000 [thread overview]
Message-ID: <20251127132249.3566-2-champbreed1@gmail.com> (raw)
In-Reply-To: <20251127132249.3566-1-champbreed1@gmail.com>
---
man/man3/getgrnam.3 | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/man/man3/getgrnam.3 b/man/man3/getgrnam.3
index 87eaf39d5..1a2143d47 100644
--- a/man/man3/getgrnam.3
+++ b/man/man3/getgrnam.3
@@ -156,12 +156,15 @@ In case of error, an error number is returned, and NULL is stored in
.IR *result .
.SH ERRORS
.TP
-.BR 0 " or " ENOENT " or " ESRCH " or " EBADF " or " EPERM " or ..."
+.BR 0
+No matching group record was found, or no error occurred (POSIX behavior).
+.TP
+.B ENOENT ", " ESRCH ", " EBADF ", " EPERM ", or other values"
The given
.I name
or
.I gid
-was not found.
+was not found. (Some UNIX implementations set errno in this case.)
.TP
.B EINTR
A signal was caught;
--
2.50.1
next prev parent reply other threads:[~2025-11-27 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 13:22 [PATCH v2 1/2] man3/getgrnam: fix ATTRIBUTES table after adding R-functions Simon Essien
2025-11-27 13:22 ` Simon Essien [this message]
2025-11-27 13:58 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2025-11-27 15:25 Simon Essien
2025-11-27 15:25 ` [PATCH v2 2/2] man3/getgrnam: clarify error behavior when entry is not found Simon Essien
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=20251127132249.3566-2-champbreed1@gmail.com \
--to=champbreed1@gmail.com \
--cc=alex@manpages.org \
--cc=linux-man@vger.kernel.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