bindat(2) [freebsd man page]
BINDAT(2) BSD System Calls Manual BINDAT(2) NAME
bindat -- assign a local protocol address to a socket LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> #include <fcntl.h> int bindat(int fd, int s, const struct sockaddr *addr, socklen_t addrlen); DESCRIPTION
The bindat() system call assigns the local protocol address to a socket. It works just like the bind(2) system call with two exceptions: 1. It is limited to sockets in the PF_LOCAL domain. 2. If the file path stored in the sun_path field of the sockaddr_un structure is a relative path, it is located relative to the directory associated with the file descriptor fd. If bindat() is passed the special value AT_FDCWD in the fd parameter, the cur- rent working directory is used and the behavior is identical to a call to bind(2). RETURN VALUES
The bindat() 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 bindat() system call may fail with the same errors as the bind(2) system call for a UNIX domain socket or with the following errors: [EBADF] The sun_path field does not specify an absolute path and the fd argument is neither AT_FDCWD nor a valid file descriptor. [ENOTDIR] The sun_path field is not an absolute path and fd is neither AT_FDCWD nor a file descriptor associated with a directory. SEE ALSO
bind(2), connectat(2), socket(2), unix(4) AUTHORS
The bindat was developed by Pawel Jakub Dawidek <pawel@dawidek.net> under sponsorship from the FreeBSD Foundation. BSD
February 13, 2013 BSD
Check Out this Related Man Page
BIND(2) BSD System Calls Manual BIND(2) NAME
bind -- bind a name to a socket SYNOPSIS
#include <sys/socket.h> int bind(int socket, const struct sockaddr *address, socklen_t address_len); 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 address 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. Consult the manual entries in section 4 for detailed information. RETURN VALUES
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. ERRORS
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 directory 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 sym- bolic 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. LEGACY SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> The include file <sys/types.h> is necessary. SEE ALSO
connect(2), getsockname(2), listen(2), socket(2), compat(5) HISTORY
The bind() function call appeared in 4.2BSD. 4.2 Berkeley Distribution June 4, 1993 4.2 Berkeley Distribution