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
Hi Chris, On 2023-08-25 03:07, bugzilla-daemon@kernel.org 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: 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. Sure. Please check the ./CONTRIBUTING file in the repository. Cheers, Alex
Patch posted at: https://lore.kernel.org/linux-man/979345cf576e86c42743ea48d797484fc41f8bf7.camel@scientia.org/T/#u