-> Click here to learn how to get live help <-
NAMEbind - bind a name to a socket
DESCRIPTIONbind gives the socket sockfd the local address my_addr. my_addr is addrlen bytes long. Traditionally, this is called (lqassigning a name to a socket.(rq When a socket is created with socket(2), it exists in a name space (address family) but has no name assigned.
It is normally necessary to assign a local address using bind before a SOCK_STREAM socket may receive connections (see accept(2)).
The rules used in name binding vary between address families. Consult the manual entries in Section 7 for detailed information. For AF_INET see ip(7), for AF_UNIX see unix(7), for AF_APPLETALK see ddp(7), for AF_PACKET see packet(7), for AF_X25 see x25(7) and for AF_NETLINK see netlink(7).
RETURN VALUEOn success, zero is returned. On error, -1 is returned, and errno is set appropriately.
The following errors are specific to UNIX domain (AF_UNIX) sockets:
BUGSThe transparent proxy options are not described.
CONFORMING TOSVr4, 4.4BSD (the bind function first appeared in BSD 4.2). SVr4 documents additional EADDRNOTAVAIL, EADDRINUSE, and ENOSR general error conditions, and additional EIO and EISDIR Unix-domain error conditions.
NOTEThe third argument of bind is in reality an int (and this is what BSD 4.* and libc4 and libc5 have). Some POSIX confusion resulted in the present socklen_t. See also accept(2).
SEE ALSOaccept(2), connect(2), listen(2), socket(2), getsockname(2), ip(7), socket(7)