Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #176
Difficulty: Easy
Apple's first product was the Apple I, invented by Apple co-founder Steve Wozniak.
True or False?
Linux & Unix Commands - Search Man Pages

bind(2) [freebsd man page]

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

NAME
bind -- assign a local protocol address to a socket LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> int bind(int s, const struct sockaddr *addr, socklen_t addrlen); DESCRIPTION
The bind() system call assigns the local protocol address to a socket. When a socket is created with socket(2) it exists in an address fam- ily space but has no protocol address assigned. The bind() system call requests that addr be assigned to the socket. NOTES
Binding an address 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 address binding vary between communication domains. Consult the manual entries in section 4 for detailed information. For maximum portability, you should always zero the socket address structure before populating it and passing it to bind(). RETURN VALUES
The bind() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate the error. ERRORS
The bind() system call will fail if: [EAGAIN] Kernel resources to complete the request are temporarily unavailable. [EBADF] The s argument is not a valid descriptor. [EINVAL] The socket is already bound to an address, and the protocol does not support binding to a new address; or the socket has been shut down. [EINVAL] The addrlen argument is not a valid length for the address family. [ENOTSOCK] The s argument is not a socket. [EADDRNOTAVAIL] The specified address is not available from the local machine. [EADDRINUSE] The specified address is already in use. [EAFNOSUPPORT] Addresses in the specified address family cannot be used with this socket. [EACCES] The requested address is protected, and the current user has inadequate permission to access it. [EFAULT] The addr argument is not in a valid part of the user address space. The following errors are specific to binding addresses in the UNIX domain. [ENOTDIR] A component of the path prefix is not a directory. [ENAMETOOLONG] A component of a pathname exceeded 255 characters, or an entire 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. SEE ALSO
connect(2), getsockname(2), listen(2), socket(2) HISTORY
The bind() system call appeared in 4.2BSD. BSD
June 26, 2014 BSD

Check Out this Related Man Page

bind(2) 							System Calls Manual							   bind(2)

Name
       bind - bind a name to a socket

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

       bind(s, name, namelen)
       int s;
       struct sockaddr *name;
       int namelen;

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

       bind(s, name, namelen)
       int s;
       struct sockaddr_un *name;
       int namelen;

Description
       The  system  call  assigns a name to an unnamed socket.	When a socket is created with the call, it exists in a name space (address family)
       but has no name assigned.  The system call requests that name 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 needed, using
       the system call.

       The sockaddr argument specifies a general address family.  The sockaddr_un argument specifies an address family in the UNIX domain.

       The  rules  used  in name binding vary between communication domains.  Consult the reference pages in the ULTRIX Reference Pages Section 4:
       Special Files for detailed information.

Return Value
       If the is successful, the call returns a 0 value.  A return value of -1 indicates an error, which is further specified in the global  vari-
       able errno.

Diagnostics
       The call fails under the following conditions:

       [EBADF]	      S is an invalid 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.

       [EACCESS]      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 exceeds 255 characters, or an entire pathname exceeds 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]       A null pathname was specified.

See Also
       connect(2), getsockname(2), listen(2), socket(2), unlink(2)

																	   bind(2)

Featured Tech Videos