Logged In: YES 
user_id=31435

I suspect the patch is close but not quite there yet.  I 
believe select will return 1 now if the socket is in *either* of 
the writable or exception sets upon select's return, so that 
the patch loses the distinction between "ok, we finally 
connected" and "oops -- we can't connect".  If so, to 
untangle that we need to pass in *distinct* sets to select, 
and when the return is > 0 it's an error case if and only if 
FS_SET then says the socket is in the exception set.  If the 
socket is in the writable set instead, then the connect 
succeeded.