BIND 10 trac2888, created. bd65ec46d25bb56ab77f50ebf8d6e431fda2d478 [2888] Close socket even on connect error

[BIND 10 source code commits]

The branch, trac2888 has been created
        at  bd65ec46d25bb56ab77f50ebf8d6e431fda2d478 (commit)

- Log -----------------------------------------------------------------
commit bd65ec46d25bb56ab77f50ebf8d6e431fda2d478
Author: Michal 'vorner' Vaner <michal.vaner at nic.cz>
Date:   Wed Apr 3 12:04:44 2013 +0200

    [2888] Close socket even on connect error
    
    Even if we fail to connect, close the socket. It is loosely related to
    the previous commit, as that one used unsuccessful connection attempts
    to discover msgq is not ready yet and the unit tests complained. It
    should have no real effect, since the garbage collector would reclaim
    the socket after a while anyway.

commit f5f3e572144232518b47dba3ed32a6cded151a47
Author: Michal 'vorner' Vaner <michal.vaner at nic.cz>
Date:   Wed Apr 3 11:59:21 2013 +0200

    [2888] Try connecting instead of looking for socket file
    
    This should solve the race condition when the socket file is created,
    but connect to it does not work yet, because listen() was not called on
    it yet. Really connecting ensures it is possible to connect.

-----------------------------------------------------------------------