text
stringlengths
0
234
above), and indicates that the file descriptor number that
is being sent is not valid (e.g., it is not an open file descriptor).
.tp
.b econnrefused
the remote address specified by
.br connect (2)
was not a listening socket.
this error can also occur if the target pathname is not a socket.
.tp
.b econnreset
remote socket was unexpectedly closed.
.tp
.b efault
user memory address was not valid.
.tp
.b einval
invalid argument passed.
a common cause is that the value
.b af_unix
was not specified in the
.i sun_type
field of passed addresses, or the socket was in an
invalid state for the applied operation.
.tp
.b eisconn
.br connect (2)
called on an already connected socket or a target address was
specified on a connected socket.
.tp
.b enoent
the pathname in the remote address specified to
.br connect (2)
did not exist.
.tp
.b enomem
out of memory.
.tp
.b enotconn
socket operation needs a target address, but the socket is not connected.
.tp
.b eopnotsupp
stream operation called on non-stream oriented socket or tried to
use the out-of-band data option.
.tp
.b eperm
the sender passed invalid credentials in the
.ir "struct ucred" .
.tp
.b epipe
remote socket was closed on a stream socket.
if enabled, a
.b sigpipe
is sent as well.
this can be avoided by passing the
.b msg_nosignal
flag to
.br send (2)
or
.br sendmsg (2).
.tp
.b eprotonosupport
passed protocol is not
.br af_unix .
.tp
.b eprototype
remote socket does not match the local socket type
.rb ( sock_dgram
versus
.br sock_stream ).
.tp
.b esocktnosupport
unknown socket type.
.tp
.b esrch
while sending an ancillary message containing credentials
.rb ( scm_credentials ),
the caller specified a pid that does not match any existing process.
.tp
.b etoomanyrefs
this error can occur for
.br sendmsg (2)
when sending a file descriptor as ancillary data over
a unix domain socket (see the description of
.br scm_rights ,
above).
it occurs if the number of "in-flight" file descriptors exceeds the
.b rlimit_nofile
resource limit and the caller does not have the
.br cap_sys_resource
capability.
an in-flight file descriptor is one that has been sent using
.br sendmsg (2)
but has not yet been accepted in the recipient process using
.br recvmsg (2).
.ip
this error is diagnosed since mainline linux 4.5
(and in some earlier kernel versions where the fix has been backported).
.\" commit 712f4aad406bb1ed67f3f98d04c044191f0ff593
in earlier kernel versions,
it was possible to place an unlimited number of file descriptors in flight,