Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bind(2) [redhat man page]

BIND(2) 						     Linux Programmer's Manual							   BIND(2)

NAME
bind - bind a name to a socket SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> int bind(int sockfd, struct sockaddr *my_addr, socklen_t addrlen); DESCRIPTION
bind gives the socket sockfd the local address my_addr. my_addr is addrlen bytes long. Traditionally, this is called "assigning a name to a socket." 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 VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately. ERRORS
EBADF sockfd is not a valid descriptor. EINVAL The socket is already bound to an address. This may change in the future: see linux/unix/sock.c for details. EACCES The address is protected, and the user is not the super-user. ENOTSOCK Argument is a descriptor for a file, not a socket. The following errors are specific to UNIX domain (AF_UNIX) sockets: EINVAL The addrlen is wrong, or the socket was not in the AF_UNIX family. EROFS The socket inode would reside on a read-only file system. EFAULT my_addr points outside the user's accessible address space. ENAMETOOLONG my_addr is too long. ENOENT The file does not exist. ENOMEM Insufficient kernel memory was available. ENOTDIR A component of the path prefix is not a directory. EACCES Search permission is denied on a component of the path prefix. ELOOP Too many symbolic links were encountered in resolving my_addr. BUGS
The transparent proxy options are not described. CONFORMING TO
SVr4, 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. NOTE
The 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 ALSO
accept(2), connect(2), listen(2), socket(2), getsockname(2), ip(7), socket(7) Linux 2.2 1998-10-03 BIND(2)

Check Out this Related Man Page

BIND(2) 						      BSD System Calls Manual							   BIND(2)

NAME
bind -- bind a name to a socket SYNOPSIS
#include <sys/socket.h> int bind(int socket, const struct sockaddr *address, socklen_t address_len); DESCRIPTION
Bind() assigns a name to an unnamed socket. When a socket is created with socket(2) it exists in a name space (address family) but has no name assigned. Bind() requests that address be assigned to the socket. NOTES
Binding a name in the UNIX domain creates a socket in the file system that must be deleted by the caller when it is no longer needed (using unlink(2)). The rules used in name binding vary between communication domains. Consult the manual entries in section 4 for detailed information. RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and the global integer variable errno is set to indicate the error. ERRORS
The bind() system call will fail if: [EACCES] The requested address is protected, and the current user has inadequate permission to access it. [EADDRINUSE] The specified address is already in use. [EADDRNOTAVAIL] The specified address is not available from the local machine. [EAFNOSUPPORT] address is not valid for the address family of socket. [EBADF] socket is not a valid file descriptor. [EDESTADDRREQ] socket is a null pointer. [EFAULT] The address parameter is not in a valid part of the user address space. [EINVAL] socket is already bound to an address and the protocol does not support binding to a new address. Alternatively, socket may have been shut down. [ENOTSOCK] socket does not refer to a socket. [EOPNOTSUPP] socket is not of a type that can be bound to an address. The following errors are specific to binding names in the UNIX domain. [EACCES] A component of the path prefix does not allow searching or the node's parent directory denies write permission. [EIO] An I/O error occurred while making the directory entry or allocating the inode. [EISDIR] An empty pathname was specified. [ELOOP] Too many symbolic links were encountered in translating the pathname. This is taken to be indicative of a looping sym- bolic link. [ENAMETOOLONG] A component of a pathname exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters. [ENOENT] A component of the path name does not refer to an existing file. [ENOTDIR] A component of the path prefix is not a directory. [EROFS] The name would reside on a read-only file system. LEGACY SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> The include file <sys/types.h> is necessary. SEE ALSO
connect(2), getsockname(2), listen(2), socket(2), compat(5) HISTORY
The bind() function call appeared in 4.2BSD. 4.2 Berkeley Distribution June 4, 1993 4.2 Berkeley Distribution
Man Page

Featured Tech Videos