Name

bind - binds a name to a socket

Library

libc.lib

Synopsis

  #include <sys/types.h>
  #include <sys/socket.h>
  int bind (int s, const struct sockaddr *addr, socklen_t addrlen);

Detailed description

The bind system call assigns the local protocol address to a socket. When a socket is created with socket 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.

Examples

#include <sys/socket.h>
#include <netinet/in.h>
#include <unistd.h>
TInt GetSockName()
{
   int sock_fd;
   struct sockaddr_in addr,ss;
   unsigned int len;   
   
   sock_fd = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);
       
   addr.sin_family = AF_INET;
   addr.sin_addr.s_addr = htonl(INADDR_ANY);
   addr.sin_port = htons(5000);
   bind(sock_fd,(struct sockaddr*)&addr,sizeof(addr));
   close(sock_fd);
}

         

Notes

For maximum portability, 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.
[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.
[EINVAL]
  The addrlen argument is not in a valid.

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, getsockname, listen, socket
The bind system call appeared in BSD 4.2 .

Feedback

For additional information or queries on this page send feedback

© 2005-2007 Nokia

Top