[Bug 217821] New: document that Linux' open(2) uses ENXIO in case of sockets, while POSIX mandates EOPNOTSUPP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxxx
          Reporter: calestyo@xxxxxxxxxxxx
        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.



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux