Error Set SendMsgError [src]

Errors

(For UNIX domain sockets, which are identified by pathname) Write permission is denied on the destination socket file, or search permission is denied for one of the directories the path prefix. (See path_resolution(7).) (For UDP sockets) An attempt was made to send to a network/broadcast address as though it was a unicast address.

AddressFamilyNotSupported

The passed address didn't have the correct address family in its sa_family field.

AddressNotAvailable

BrokenPipe SendError

The local end has been shut down on a connection oriented socket. In this case, the process will also receive a SIGPIPE unless MSG.NOSIGNAL is set.

ConnectionResetByPeer SendError

Connection reset by peer.

FastOpenAlreadyInProgress SendError

Another Fast Open is already in progress.

FileDescriptorNotASocket SendError

FileNotFound

Returned when socket is AF.UNIX and the given path does not point to an existing file.

MessageTooBig SendError

The socket type requires that message be sent atomically, and the size of the message to be sent made this impossible. The message is not transmitted.

NameTooLong

Returned when socket is AF.UNIX and the given path length exceeds max_path_bytes bytes.

NetworkSubsystemFailed SendError

The local network interface used to reach the destination is down.

NetworkUnreachable SendError

Network is unreachable.

NotDir

SocketNotConnected

The socket is not connected (connection-oriented sockets only).

SymLinkLoop

Returned when socket is AF.UNIX and the given path has a symlink loop.

SystemResources SendError

The output queue for a network interface was full. This generally indicates that the interface has stopped sending, but may be caused by transient congestion. (Normally, this does not occur in Linux. Packets are just silently dropped when a device queue overflows.) This is also caused when there is not enough kernel memory available.

Unexpected UnexpectedError

The Operating System returned an undocumented error code.

This error is in theory not possible, but it would be better to handle this error than to invoke undefined behavior.

When this error code is observed, it usually means the Zig Standard Library needs a small patch to add the error code to the error set for the respective function.

WouldBlock SendError

The socket is marked nonblocking and the requested operation would block, and there is no global event loop configured. It's also possible to get this error under the following condition: (Internet domain datagram sockets) The socket referred to by sockfd had not previously been bound to an address and, upon attempting to bind it to an ephemeral port, it was determined that all port numbers in the ephemeral port range are currently in use. See the discussion of /proc/sys/net/ipv4/ip_local_port_range in ip(7).

Source

  pub const SendMsgError = SendError || error{
    /// The passed address didn't have the correct address family in its sa_family field.
    AddressFamilyNotSupported,

    /// Returned when socket is AF.UNIX and the given path has a symlink loop.
    SymLinkLoop,

    /// Returned when socket is AF.UNIX and the given path length exceeds `max_path_bytes` bytes.
    NameTooLong,

    /// Returned when socket is AF.UNIX and the given path does not point to an existing file.
    FileNotFound,
    NotDir,

    /// The socket is not connected (connection-oriented sockets only).
    SocketNotConnected,
    AddressNotAvailable,
}  