summaryrefslogtreecommitdiff
path: root/man2/connect.2
blob: a1307f49ab38c1b0bc6e25be27b18aa2aa97c5fc (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
.\" Hey Emacs! This file is -*- nroff -*- source.
.\"
.\" Copyright 1993 Rickard E. Faith (faith@cs.unc.edu)
.\" Portions extracted from /usr/include/sys/socket.h, which does not have
.\" any authorship information in it.  It is probably available under the GPL.
.\"
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\"
.\" Permission is granted to copy and distribute modified versions of this
.\" manual under the conditions for verbatim copying, provided that the
.\" entire resulting derived work is distributed under the terms of a
.\" permission notice identical to this one.
.\" 
.\" Since the Linux kernel and libraries are constantly changing, this
.\" manual page may be incorrect or out-of-date.  The author(s) assume no
.\" responsibility for errors or omissions, or for damages resulting from
.\" the use of the information contained herein.  The author(s) may not
.\" have taken the same level of care in the production of this manual,
.\" which is licensed free of charge, as they might when working
.\" professionally.
.\" 
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.\"
.\" Other portions are from the 6.9 (Berkeley) 3/10/91 man page:
.\"
.\" Copyright (c) 1983 The Regents of the University of California.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\"    must display the following acknowledgement:
.\"     This product includes software developed by the University of
.\"     California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" Modified 1997-01-31 by Eric S. Raymond <esr@thyrsus.com>
.\" Modified 1998, 1999 by Andi Kleen
.\" Modified 2004-06-23 by Michael Kerrisk <mtk-manpages@gmx.net>
.\"
.TH CONNECT 2 2004-06-23 "Linux 2.6.7" "Linux Programmer's Manual"
.SH NAME
connect \- initiate a connection on a socket
.SH SYNOPSIS
.B #include <sys/types.h>
.br
.B #include <sys/socket.h>
.sp
.BI "int connect(int " sockfd ", const struct sockaddr *" serv_addr ,
.BI "socklen_t " addrlen );
.SH DESCRIPTION
The
.BR connect ()
system call connects the socket referred to by the file descriptor
.I sockfd
to the address specified by
.IR serv_addr .
The
.IR addrlen 
argument specifies the size of
.IR serv_addr .
The format of the address in
.I serv_addr
is determined by the address space of the socket
.IR sockfd ;
see
.BR socket (2)
for further details.

If the socket
.I sockfd
is of type
.B SOCK_DGRAM
then
.I serv_addr
is the address to which datagrams are sent by default, and the only
address from which datagrams are received.  If the socket is of type
.B SOCK_STREAM
or
.BR SOCK_SEQPACKET ,
this call attempts to make a connection to the socket that is bound
to the address specified by
.IR serv_addr .
.PP
Generally, connection-based protocol sockets may successfully
.BR connect ()
only once; connectionless protocol sockets may use
.BR connect ()
multiple times to change their association.  Connectionless sockets may
dissolve the association by connecting to an address with the 
.I sa_family
member of
.B sockaddr 
set to 
.BR AF_UNSPEC .
.SH "RETURN VALUE"
If the connection or binding succeeds, zero is returned.  On error, \-1 is
returned, and
.I errno
is set appropriately.
.SH ERRORS
The following are general socket errors only.  There may be other
domain-specific error codes. 
.TP
.B EACCES
For Unix domain sockets, which are identified by pathname:
Write permission is denied on the socket file,
or search permission is denied for one of the directories
in the path prefix.
(See also
.BR path_resolution (2).)
.TP
.B EACCES, EPERM
The user tried to connect to a broadcast address without having the socket 
broadcast flag enabled or the connection request failed because of a local
firewall rule.
.TP
.B EADDRINUSE
Local address is already in use.
.TP
.B EAFNOSUPPORT
The passed address didn't have the correct address family in its 
.I sa_family
field.
.TP
.B EAGAIN
No more free local ports or insufficient entries in the routing cache. For
.B PF_INET
see the 
.B net.ipv4.ip_local_port_range
sysctl in 
.BR ip (7) 
on how to increase the number of local ports.
.TP
.B EALREADY
The socket is non-blocking and a previous connection attempt has not yet
been completed.
.TP
.B EBADF
The file descriptor is not a valid index in the descriptor table.
.TP
.B ECONNREFUSED
No one listening on the remote address.
.TP
.B EFAULT
The socket structure address is outside the user's address space.
.TP
.B EINPROGRESS
The socket is non-blocking and the connection cannot be completed
immediately.  It is possible to
.BR select (2)
or 
.BR poll (2) 
for completion by selecting the socket for writing. After 
.B select
indicates writability, use
.BR getsockopt (2)
to read the 
.B SO_ERROR
option at level 
.B SOL_SOCKET
to determine whether 
.BR connect ()
completed successfully 
.RB ( SO_ERROR
is zero) or unsuccessfully 
.RB ( SO_ERROR
is one of the usual error codes listed here, 
explaining the reason for the failure).
.TP
.B EINTR
The system call was interrupted by a signal that was caught.
.\" For TCP, the connection will complete asynchronously.
.\" See http://lkml.org/lkml/2005/7/12/254
.TP
.B EISCONN
The socket is already connected.
.TP
.B ENETUNREACH
Network is unreachable.
.TP
.B ENOTSOCK
The file descriptor is not associated with a socket.
.TP
.B ETIMEDOUT
Timeout while attempting connection. The server may be too 
busy to accept new connections. Note that for IP sockets the timeout may
be very long when syncookies are enabled on the server.
.SH "CONFORMING TO"
SVr4, 4.4BSD (the
.BR connect ()
function first appeared in 4.2BSD).  SVr4 documents the additional
general error codes 
.BR EADDRNOTAVAIL , 
.BR EINVAL , 
.BR EAFNOSUPPORT , 
.BR EALREADY , 
.BR EINTR , 
.BR EPROTOTYPE , 
and
.BR ENOSR .  
It also
documents many additional error conditions not described here.
.SH NOTE
The third argument of
.BR connect ()
is in reality an
.I int
(and this is what 4.x BSD and libc4 and libc5 have).
Some POSIX confusion resulted in the present 
.IR socklen_t ,
also used by glibc.
See also
.BR accept (2).
.SH BUGS
Unconnecting a socket by calling
.BR connect ()
with a
.B AF_UNSPEC
address is not yet implemented.
.SH "SEE ALSO"
.BR accept (2),
.BR bind (2),
.BR getsockname (2),
.BR listen (2),
.BR path_resolution (2),
.BR socket (2)