From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 217821] New: document that Linux' open(2) uses ENXIO in case of sockets, while POSIX mandates EOPNOTSUPP
Date: Fri, 25 Aug 2023 01:07:08 +0000 [thread overview]
Message-ID: <bug-217821-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217821
Bug ID: 217821
Summary: document that Linux' open(2) uses ENXIO in case of
sockets, while POSIX mandates EOPNOTSUPP
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P3
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: calestyo@scientia.org
Regression: No
Hey.
It seems that under Linux, when using a socket file with the open(2) family of
functions, the error is:
> ENXIO The file is a UNIX domain socket.
OTOH, POSIX specifies[0]:
> [EOPNOTSUPP]
> The path argument names a socket.
Maybe it makes sense to document that? Possibly right at the ENXIO descripton
and even additionally in the STANDARDS section?
I could write a patch if you tell me which you like.
Cheers,
Chris.
[0] https://pubs.opengroup.org/onlinepubs/9699919799/functions/open.html
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-08-25 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 1:07 bugzilla-daemon [this message]
2023-08-25 10:19 ` [Bug 217821] New: document that Linux' open(2) uses ENXIO in case of sockets, while POSIX mandates EOPNOTSUPP Alejandro Colomar
2023-08-25 10:19 ` [Bug 217821] " bugzilla-daemon
2023-08-25 20:30 ` bugzilla-daemon
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=bug-217821-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.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;
as well as URLs for NNTP newsgroup(s).