Mac Developer Library Developer


This manual page is part of Xcode Tools version 5.0

To obtain these tools:

If you are running a version of Xcode Tools other than 5.0, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

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

     bind -- bind a name to a socket

     #include <sys/socket.h>

     bind(int socket, const struct sockaddr *address, socklen_t address_len);

     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

     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 sec-tion section
     tion 4 for detailed information.

     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.

     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 direc-tory directory
                        tory 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 symbolic 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.

     #include <sys/types.h>
     #include <sys/socket.h>

     The include file <sys/types.h> is necessary.

     connect(2), getsockname(2), listen(2), socket(2), compat(5)

     The bind() function call appeared in 4.2BSD.

4.2 Berkeley Distribution        June 4, 1993        4.2 Berkeley Distribution

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.