Yury Selivanov added the comment:
Hm, maybe I'm mistaken here, but I have no time right now to confirm.
I'll reopen the issue so that we can consider this (and especially SEQPACKET)
for 3.8. Sorry for insta-reject :)
--
resolution: rejected ->
stage: resolved ->
status: closed -> o
holger added the comment:
Could you please tell me which exact posix document and paragraph says that?
In Linux sending can fail but once sendmsg worked the message is enqueued on
the other socket
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/unix/af_unix.c?id=1
Yury Selivanov added the comment:
SOCK_DGRAM is never reliable, even for AF_UNIX. It might appear reliable to
your test code, but there's no guarantee for that under any OS in Posix
standard AFAIK.
--
resolution: -> rejected
stage: -> resolved
status: open -> closed
__
New submission from holger :
The current implementation verifies that the sock passed is a stream socket.
This limitation appears to be arbitrary and is limiting.
* An AF_UNIX SOCK_DGRAM server socket becomes readable when one can accept(2)
it. Just like SOCK_STREAM.
* One could provide a diff
