4.4BSD/usr/share/man/cat2/bind.0

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

NNAAMMEE
     bbiinndd - bind a name to a socket

SSYYNNOOPPSSIISS
     ##iinncclluuddee <<ssyyss//ttyyppeess..hh>>
     ##iinncclluuddee <<ssyyss//ssoocckkeett..hh>>

     _i_n_t
     bbiinndd(_i_n_t _s, _s_t_r_u_c_t _s_o_c_k_a_d_d_r _*_n_a_m_e, _i_n_t _n_a_m_e_l_e_n);

DDEESSCCRRIIPPTTIIOONN
     BBiinndd() 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.  BBiinndd() requests that _n_a_m_e be assigned to the socket.

NNOOTTEESS
     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.  Con-
     sult the manual entries in section 4 for detailed information.

RREETTUURRNN VVAALLUUEESS
     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 _e_r_r_n_o.

EERRRROORRSS
     The bbiinndd() 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 ma-
                  chine.

     [EADDRINUSE]
                  The specified address is already in use.

     [EINVAL]     The socket is already bound to an address.

     [EACCES]     The requested address is protected, and the current user has
                  inadequate permission to access it.

     [EFAULT]     The _n_a_m_e parameter is not in a valid part of the user ad-
                  dress space.

     The following errors are specific to binding names in the UNIX domain.

     [ENOTDIR]    A component of the path prefix is not a directory.

     [EINVAL]     The pathname contains a character with the high-order bit
                  set.

     [ENAMETOOLONG]
                  A component of a pathname exceeded 255 characters, or an en-
                  tire path name exceeded 1023 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.

SSEEEE AALLSSOO
     connect(2),  listen(2),  socket(2),  getsockname(2)

HHIISSTTOORRYY
     The bbiinndd function call appeared in 4.2BSD.

4.2 Berkeley Distribution        June 4, 1993                                2