connect() does not return ETIMEDOUT

Manfred Bartz (mbartz@optushome.com.au)
14 Aug 2001 00:00:49 +1000


When a TCP client opens multiple connections beyond the server's
backlog capacity, the call to connect() returns a value of zero
(success) after 9 seconds. Toggling SYN-cookies makes no difference.

Is this intended behaviour?

Under Solaris I get ETIMEDOUT (Connection timed out) after a little
less than 4 minutes.

Presumably I could set the socket to non-blocking and select() for
writability... (I have not tested that yet.)

But if I want to keep it simple, what is the recommended solution?

-- 
Manfred Bartz

- 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/