New: document that Linux' open(2) uses ENXIO in case of sockets, while POSIX mandates EOPNOTSUPP
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: [email protected]
Reporter: [email protected]
Regression: No
Hey.
It seems that under Linux, when using a socket file with the open(2) family of functions, the error is:
Quoted 1 line
ENXIO The file is a UNIX domain socket.
OTOH, POSIX specifies[0]:
Quoted 2 lines
[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
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
Hi Chris,
Quoted 24 lines · On 2023-08-25 03:07, [email protected] wrote:
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: [email protected]
Reporter: [email protected]
Regression: NoHey.
It seems that under Linux, when using a socket file with the open(2) family of functions, the error is:
Quoted 1 line
ENXIO The file is a UNIX domain socket.
OTOH, POSIX specifies[0]:
Quoted 8 lines
Quoted 2 lines
[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.
Sure. Please check the ./CONTRIBUTING file in the repository.
Cheers,
Alex
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[Bug 217821] document that Linux' open(2) uses ENXIO in case of sockets, while POSIX mandates EOPNOTSUPP
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=217821
--- Comment #1 from Alejandro Colomar ([email protected]) --- Hi Chris,
Quoted 25 lines · On 2023-08-25 03:07, [email protected] wrote:
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: [email protected]
Reporter: [email protected]
Regression: NoHey.
It seems that under Linux, when using a socket file with the open(2) family of
functions, the error is:Quoted 1 line
ENXIO The file is a UNIX domain socket.
OTOH, POSIX specifies[0]:
Quoted 8 lines
Quoted 2 lines
[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.
Sure. Please check the ./CONTRIBUTING file in the repository.
Cheers,
Alex
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 217821] document that Linux' open(2) uses ENXIO in case of sockets, while POSIX mandates EOPNOTSUPP
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=217821
--- Comment #2 from Christoph Anton Mitterer ([email protected]) --- Patch posted at:
https://lore.kernel.org/linux-man/[email protected]/T/#u
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.