*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->FreeBSD man pages -> bind (2)              
Title
Content
Arch
Section
 

BIND(2)

Contents


NAME    [Toc]    [Back]

     bind -- assign a local protocol address to a socket

LIBRARY    [Toc]    [Back]

     Standard C Library (libc, -lc)

SYNOPSIS    [Toc]    [Back]

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

     int
     bind(int s, const struct sockaddr *addr, socklen_t addrlen);

DESCRIPTION    [Toc]    [Back]

     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 family
     space but has no protocol address assigned.  The bind() system call
     requests that addr be assigned to the socket.

NOTES    [Toc]    [Back]

     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    [Toc]    [Back]

     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    [Toc]    [Back]

     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.

     [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.

     [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    [Toc]    [Back]

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

HISTORY    [Toc]    [Back]

     The bind() system call appeared in 4.2BSD.


FreeBSD 5.2.1			 June 4, 1993			 FreeBSD 5.2.1
[ Back ]
 Similar pages
Name OS Title
inet_lnaof Tru64 Translate an Internet address integer into its host (local) address component
getsockname HP-UX get socket address
bind HP-UX bind an address to a socket
net_addrcmp OpenBSD compare socket address structures
rresvport_af Tru64 Retrieve a socket with a privileged address
rresvport Tru64 Retrieve a socket with a privileged address
wire-test FreeBSD test your network interfaces and local IP address
rpccp_add_mapping HP-UX Adds or replaces server address information in the local endpoint map
show_cached_server HP-UX Displays address information of a server in the local clerk's cache
rapi_getfd Tru64 Get the file descriptor for the Resource ReSerVation Protocol (RSVP) daemon's socket
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service