Bind man page on 4.4BSD

Man page or keyword search:  
man Server   1065 pages
apropos Keyword Search (all sections)
Output format
4.4BSD logo
[printable version]

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

NAME
     bind — bind a name to a socket

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

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

DESCRIPTION
     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 name be assigned to the socket.

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

RETURN VALUES
     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 errno.

ERRORS
     The bind() 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
		  machine.

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

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

     [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), listen(2), socket(2), getsockname(2)

HISTORY
     The bind function call appeared in 4.2BSD.

4.2 Berkeley Distribution	 June 4, 1993	     4.2 Berkeley Distribution
[top]

List of man pages available for 4.4BSD

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net