Index of Section 2 Manual Pages

Interix / SUAaccept.2Interix / SUA

accept(2)                                                     accept(2)

  accept()

  NAME

    accept() - accept a connection on a socket

  SYNOPSIS

    #include 
    #include 

    int accept (int socket, struct sockaddr *addr, int *addrlen)

  DESCRIPTION

    The argument socket is a socket that has been created with socket(2),
    bound to an address with bind(2), and is listening for connections after a
    listen(2). The accept(2) argument extracts the first connection request on
    the queue of pending connections, creates a new socket with the same
    properties of socket and allocates a new file descriptor for the socket.
    If no pending connections are present on the queue and the socket is not
    marked as non-blocking, accept(2) blocks the caller until a connection is
    present. If the socket is marked non-blocking and no pending connections
    are present on the queue, accept(2) returns an error as described below.
    The accepted socket may not be used to accept more connections. The
    original socket identified by the socket argument remains open.

    If addr and addrlen are both non-NULL, accept(2) fills the argument addr
    with the address of the connecting entity, as known to the communications
    layer. The exact format of the addr parameter is determined by the domain
    in which the communication is occurring. The addrlen is a value-result
    parameter; it should initially contain the amount of space pointed to by
    addr; on return it will contain the actual length (in bytes) of the
    address returned. This call is used with connection-based socket types,
    such as SOCK_STREAM.

    If either argument is null, no information is returned.

    You can select(2) a socket for the purposes of doing an accept(2) by
    selecting it for read.

  RETURN VALUES

    The call returns -1 on error. If it succeeds, it returns a non-negative
    integer that is a descriptor for the accepted socket.

  ERRORS

    The accept(2) will fail if:

    [EBADF]
        The descriptor is invalid.

    [ENOTSOCK]
        The descriptor references a file, not a socket.

    [EOPNOTSUPP]
        The referenced socket is not of type SOCK_STREAM.

    [EFAULT]
        The addr parameter is not in a writable part of the user address
        space.

    [EWOULDBLOCK]

        The socket is marked non-blocking and no connections are present to be
        accepted.

  SEE ALSO

    bind(2)

    connect(2)

    listen(2)

    select(2)

    socket(2)

  USAGE NOTES

    The accept function is thread safe.

    The accept function is async-signal safe.


Interix / SUAHosted at SUA Community for Interix, SUA and SFUInterix / SUA