icon Top 9 categories map      RocketAware > man pages >


Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.

The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Search all pages


By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Integer, Floating point, Matrix, Statistics, Boolean, ...

Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...


RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD RedHat Others

CONNECT(2)                OpenBSD Programmer's Manual               CONNECT(2)

     connect - initiate a connection on a socket

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

     connect(int s, const struct sockaddr *name, socklen_t namelen);

     The parameter s is a socket.  If it is of type SOCK_DGRAM, this call
     specifies the peer with which the socket is to be associated; this ad-
     dress is that to which datagrams are to be sent, and the only address
     from which datagrams are to be received.  If the socket is of type
     SOCK_STREAM, this call attempts to make a connection to another socket.
     The other socket is specified by name, which is an address in the commu-
     nications space of the socket.  Each communications space interprets the
     name parameter in its own way.  Generally, stream sockets may successful-
     ly connect() only once; datagram sockets may use connect() multiple times
     to change their association.  Datagram sockets may dissolve the associa-
     tion by connecting to an invalid address, such as a null address.

     If the connection or binding succeeds, 0 is returned.  Otherwise a -1 is
     returned, and a more specific error code is stored in errno.

     The connect() call fails if:

     [EBADF]       S is not a valid descriptor.

     [ENOTSOCK]    S is a descriptor for a file, not a socket.

                   The specified address is not available on this machine.

                   Addresses in the specified address family cannot be used
                   with this socket.

     [EISCONN]     The socket is already connected.

     [ETIMEDOUT]   Connection establishment timed out without establishing a

     [EINVAL]      A TCP connection with a local broadcast, the all-ones or a
                   multicast address as the peer was attempted.

                   The attempt to connect was forcefully rejected.

     [EINTR]       A connect was interrupted before it succeeded by the deliv-
                   ery of a signal.

                   The network isn't reachable from this host.

     [EADDRINUSE]  The address is already in use.

     [EFAULT]      The name parameter specifies an area outside the process

                   address space.

                   The socket is non-blocking and the connection cannot be
                   completed immediately.  It is possible to select(2) or
                   poll(2) for completion by selecting the socket for writing,
                   and also use getsockopt(2) with SO_ERROR to check for error

     [EALREADY]    The socket is non-blocking and a previous connection at-
                   tempt has not yet been completed.

     The following errors are specific to connecting names in the UNIX domain.
     These errors may not apply in future versions of the UNIX IPC domain.

     [ENOTDIR]     A component of the path prefix is not a directory.

                   A component of a pathname exceeded {NAME_MAX} characters,
                   or an entire path name exceeded {PATH_MAX} characters.

     [ENOENT]      The named socket does not exist.

     [EACCES]      Search permission is denied for a component of the path

     [EACCES]      Write access to the named socket is denied.

     [ELOOP]       Too many symbolic links were encountered in translating the

     accept(2),  getsockname(2),  getsockopt(2),  poll(2),  select(2),  sock-

     The connect() function call appeared in 4.2BSD.

OpenBSD 2.6                    February 15, 1999                             2

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.

(Corrections, notes, and links courtesy of RocketAware.com)

[Detailed Topics]

[Overview Topics]

Up to: Socket and I/O Operations - socket() and related functions.

RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD RedHat Others

Rapid-Links: Search | About | Comments | Submit Path: RocketAware > man pages > connect.2/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments