connect() to localhost non-blocking.

• Next message: Doug McNaught: "Re: connect() to localhost non-blocking."
• Previous message: Vojtech Pavlik: "Re: VIA 686b Bug - once again :("
• Next in thread: Doug McNaught: "Re: connect() to localhost non-blocking."
• Maybe reply: Doug McNaught: "Re: connect() to localhost non-blocking."
• Maybe reply: Dan Kegel: "Re: connect() to localhost non-blocking."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hallo all,

I wrote a little test program to do some poll() benchmarks.
I changed the host address to localhost and observed that
connect() always returns EINPROGRESS when used with non-blocking
sockets.

>From the man page:

EINPROGRESS
 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.

So my question is:

What is meant by 'cannot be completed immediately' ?
I thought that connections to localhost would complete
without any delay when the application listens ?

thanks for your answers,
Patrick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Doug McNaught: "Re: connect() to localhost non-blocking."
• Previous message: Vojtech Pavlik: "Re: VIA 686b Bug - once again :("
• Next in thread: Doug McNaught: "Re: connect() to localhost non-blocking."
• Maybe reply: Doug McNaught: "Re: connect() to localhost non-blocking."
• Maybe reply: Dan Kegel: "Re: connect() to localhost non-blocking."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Oct 23 2001 - 21:00:28 EST