This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Slon
Recipients Slon
Date 2018-08-22.21:04:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1534971851.11.0.56676864532.issue34466@psf.upfronthosting.co.za>
In-reply-to
Content
Attached program creates listening server socket, fills backlog queue with 2 client socket and performs third connect attempt after setting socket timeout to 5 second.

I expect third connect() attempt to fail after specified timeout of 5 second. That is indeed what's happening for tcp socket (AF_INET).

But when underlying socket has type AF_UNIX, connect() fails immediately with 'Resource temporarily unavailable' error. I'm able to reproduce this issue on linux 4.17.12 and python 3.6.6.

The underlying issue seems to be different behavior of connect(3) system call for unix sockets. Instead of starting operation and returning EINPROGRESS error it fails immediately with EAGAIN error.

Thanks to Vladislav Bidzilya for discovering this issue.
History
Date User Action Args
2018-08-22 21:04:11Slonsetrecipients: + Slon
2018-08-22 21:04:11Slonsetmessageid: <1534971851.11.0.56676864532.issue34466@psf.upfronthosting.co.za>
2018-08-22 21:04:11Slonlinkissue34466 messages
2018-08-22 21:04:10Sloncreate