Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bind(3socket) [sunos man page]

bind(3SOCKET)						     Sockets Library Functions						     bind(3SOCKET)

NAME
bind - bind a name to a socket SYNOPSIS
cc [ flag ... ] file ... -lsocket -lnsl [ library ... ] #include <sys/types.h> #include <sys/socket.h> int bind(int s, const struct sockaddr *name, int namelen); DESCRIPTION
bind() assigns a name to an unnamed socket. When a socket is created with socket(3SOCKET), it exists in a name space (address family) but has no name assigned. bind() requests that the name pointed to by name be assigned to the socket. RETURN VALUES
If the bind is successful, 0 is returned. A return value of -1 indicates an error, which is further specified in the global errno. ERRORS
The bind() call will fail if: EACCES The requested address is protected, and {PRIV_NET_PRIVADDR} is not asserted in the effective set of the current process. EADDRINUSE The specified address is already in use. EADDRNOTAVAIL The specified address is not available on the local machine. EBADF s is not a valid descriptor. EINVAL namelen is not the size of a valid address for the specified address family. EINVAL The socket is already bound to an address. ENOSR There were insufficient STREAMS resources for the operation to complete. ENOTSOCK s is a descriptor for a file, not a socket. The following errors are specific to binding names in the UNIX domain: EACCES Search permission is denied for a component of the path prefix of the pathname in name. EIO An I/O error occurred while making the directory entry or allocating the inode. EISDIR A null pathname was specified. ELOOP Too many symbolic links were encountered in translating the pathname in name. ENOENT A component of the path prefix of the pathname in name does not exist. ENOTDIR A component of the path prefix of the pathname in name is not a directory. EROFS The inode would reside on a read-only file system. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
unlink(2), socket(3SOCKET), attributes(5), privileges(5), socket.h(3HEAD) 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 byus- ing unlink(2). The rules used in name binding vary between communication domains. SunOS 5.10 20 Feb 2003 bind(3SOCKET)

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