bind - bind a name to a socket
#include <sys/types.h>
#include <sys/socket.h>
int
bind(int s, const struct sockaddr *name, socklen_t namelen);
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 name be assigned to the
socket. namelen
indicates the amount of space pointed to by name, in bytes.
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.
If the bind is successful, a 0 value is returned. A return
value of -1
indicates an error, which is further specified in the global
errno.
The bind() call will fail if:
[EBADF] S is not a valid descriptor.
[ENOTSOCK] S is not a socket.
[EADDRNOTAVAIL]
The specified address is not available from
the local machine.
[EADDRINUSE] The specified address is already in use.
[EINVAL] The socket is already bound to an address.
[EINVAL] The family of the socket and that requested in
name->sa_family are not equivalent.
[EACCES] The requested address is protected, and the
current user
has inadequate permission to access it.
[EFAULT] The name parameter is not in a valid part of
the user address
space.
The following errors are specific to binding names in the
UNIX domain.
[ENOTDIR] A component of the path prefix is not a directory.
[ENAMETOOLONG]
A component of a pathname exceeded {NAME_MAX}
characters,
or an entire path name exceeded {PATH_MAX}
characters.
[ENOENT] A prefix component of the path name does not
exist.
[ELOOP] Too many symbolic links were encountered in
translating the
pathname.
[EIO] An I/O error occurred while making the directory entry or
allocating the inode.
[EROFS] The name would reside on a read-only file system.
[EISDIR] An empty pathname was specified.
connect(2), getsockname(2), listen(2), socket(2)
The bind() function call appeared in 4.2BSD.
OpenBSD 3.6 February 15, 1999
[ Back ] |