[usocket-devel] bug in backend/sbcl.lisp ?

[Anton Kovalenko]

Robert Brown <robert.brown at gmail.com> writes:

> With the current code, when I create a lot of client stream
> sockets on a Linux system, the bind call in socket-connect
> eventually returns an error, address already in use.  I don't
> think the bind call is needed for the client end of stream
> sockets.

Bind is not needed unless we want a specific interface or a specific
client port.

USOCKET code seems to take /some/ care of not calling bind() unless
it's needed; however, *wildcard-host* and *auto-port* being non-NIL 
makes bind() happen.

(I guess that the underlying problem will go away if SO_REUSEADDR will be
enabled on client socket, i.e. explicit bind() will succeed then).

-- 
Regards, Anton Kovalenko
+7(916)345-34-02 | Elektrostal' MO, Russia