.\" Copyright (c) 1983 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)bind.2 6.6 (Berkeley) %G%
bind \- bind a name to a socket
assigns a name to an unnamed socket.
it exists in a name space (address family)
but has no name assigned.
be assigned to the socket.
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
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 \fIerrno\fP.
The \fIbind\fP call will fail if:
\fIS\fP is not a valid descriptor.
The specified address is not available from the local machine.
The specified address is already in use.
The socket is already bound to an address.
The requested address is protected, and the current user
has inadequate permission to access it.
The \fIname\fP parameter is not in a valid part of the user
The following errors are specific to binding names in the UNIX domain.
A component of the path prefix is not a directory.
The pathname contains a character with the high-order bit set.
A component of a pathname exceeded 255 characters,
or an entire path name exceeded 1023 characters.
A prefix component of the path name does not exist.
Too many symbolic links were encountered in translating the pathname.
An I/O error occurred while making the directory entry or allocating the inode.
The name would reside on a read-only file system.
A null pathname was specified.
connect(2), listen(2), socket(2), getsockname(2)