Handle Errno::ENOTCONN when testing for sshd access

[eugenebolshakov]

I got a Errno::ENOTCONN when running knife via tsocks (transparent SOCKS proxy) and I think it should be handled as a valid exception while waiting for SSHD to become available. ENOTCONN means 'Transport endpoint is not connected'.

BTW, I saw this issue #367 about guidelines for contributing being outdated and that's why I didn't create a ticket in JIRA, etc. Please let me know if I need to.

Thanks!

[chef-supermarket]

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.

GitHub Users Who Are Not Authorized To Contribute

The following GitHub users do not appear to have signed a CLA:

• @eugenebolshakov

Please sign the CLA here.

[chef-supermarket]

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

[btm]

Interesting, tsocks appears to be ancient and the use of ENOTCONN is in debian patches. I don't see any reason not to include it.