Sponsored Content
Top Forums Programming Looping connect call for a non blocking socket Post 302705037 by achenle on Monday 24th of September 2012 06:33:13 AM
Old 09-24-2012
The code as written will not work as you expect if the initial connect() call fails with EALREADY or EINPROGRESS.

You need to reset errno to zero before each connect call.

Successful system calls will not change the value of errno.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Blocking ftp users to connect using telnet

Hi everybody ! We have all flavors of Unix / Linux and we want to restrict ftp users to telnet our servers. We can't disable telnet because we have other users using it. :confused: Are there any thing that could be done to solve this thing ??? Best regards, Julio Moreira (11 Replies)
Discussion started by: juliocdrm
11 Replies

2. Shell Programming and Scripting

Looping connect to different server

Hi there. I am attempting to write a script that will read through a flat file, get the server and directory that I want the size for, connect to the server, get the directory size, and send it to an output file. Here is what I have: while read LINE do NAME=`echo $LINE | awk -F'~' '{print... (5 Replies)
Discussion started by: la_womn
5 Replies

3. UNIX for Advanced & Expert Users

connect problem for sctp socket (ipv6 socket) - Runtime fail Invalid Arguments

Hi, I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime. To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies

4. Programming

connect() socket API

Is there any relation between the connect() socket API and the TCP's Transmission Control Block. Also how does connect detect that a socket is in use i.e., EADDRINUSE (1 Reply)
Discussion started by: sunaina
1 Replies

5. Solaris

Non-blocking connect readability & writeability

Hello, When using a non-blocking connect, is it _guaranteed_ that connection completion can be detected by selecting for writeability? I have encountered situations where the socket has returned both readable and writeable at the same time - having trawled the net, I have seen some old posts... (1 Reply)
Discussion started by: tristan12
1 Replies

6. Programming

non blocking connect

OS : solaris 10 X86 I created stream socket, tries to connect to port 7 on the remote machine. After doing the non blocking connect call I did select with time out value is 3 secs. I am always getting timed out though I am writing prior to select. code: x=fcntl(S,F_GETFL,0);... (1 Reply)
Discussion started by: satish@123
1 Replies

7. Programming

write on Non Blocking Socket

How to know whether socket is ready for write. select(maxfds, (fd_set *)NULL, &writefds, NULL, &timeout); By default socket is set for write without checking whether it would block or not? If so how do I know my FD is ready for writing. (3 Replies)
Discussion started by: satish@123
3 Replies

8. Programming

socket accept() keeps looping

I'm using C/ C++ with gcc on Linux. I've a server socket where accept() is called on the socket inside a while() loop. The problem I am facing is that the first call to accept is blocking (i.e., the program waits for the first connection) but as soon as I fork afterwards (so that the child process... (2 Replies)
Discussion started by: jaywalker
2 Replies

9. Programming

Looping problems socket programming in C

Sorry if I posted 2 separate questions. I'm currently doing socket programming on my current task. As you can see below in the client side. I've tried to do a loop so I will be able to get prompt for input over and over again. This is the code. do{ printf("Please your name > ");... (10 Replies)
Discussion started by: aLHaNz
10 Replies

10. UNIX for Dummies Questions & Answers

Cannot connect to socket

solaris client report "cannot to socket(code 25)" while trying to backup on veritas netbackup 6.5.5 server (1 Reply)
Discussion started by: EUGINIAM
1 Replies
connect(2)							System Calls Manual							connect(2)

Name
       connect - initiate a connection on a socket

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

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

Description
       The  call  initiates  a	connection  on a socket.  The parameter s is a socket.	If the socket is of type SOCK_DGRAM, this call permanently
       specifies the peer to which datagrams are sent.	If it 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 communications space of the socket.  Each communications space interprets
       the name parameter in its own way.  The size of the structure sockaddr is namelen.

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

Diagnostics
       The call fails under the following conditions:

       [EBADF]	      The s is not a valid descriptor.

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

       [EADDRNOTAVAIL]
		      The specified address is not available on this machine.

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

       [EINPROGRESS]  The connection is requested on a socket with FNDELAY set (using

       [EISCONN]      The socket is already connected.

       [ETIMEDOUT]    Connection establishment timed out without establishing a connection.

       [ECONNREFUSED] The attempt to connect was forcefully rejected.

       [ENETUNREACH]  The network is not reachable from this host.

       [EADDRINUSE]   The address is already in use.

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

       [EWOULDBLOCK]  The socket is nonblocking, and the connection cannot be completed immediately.  You can select the  socket  for  writing	by
		      using the system call while it is connecting.

       The following errors are specific to connecting names in the ULTRIX 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]       The named socket does not exist.

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

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

See Also
       accept(2), fcntl(2), getsockname(2), select(2), shutdown(2), socket(2)

																	connect(2)
All times are GMT -4. The time now is 12:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy