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 socketpair
Recipients giampaolo.rodola, segfaulthunter, socketpair
Date 2011-03-05.05:09:44
SpamBayes Score 1.1925322e-10
Marked as misclassified No
Message-id <1299301786.07.0.989325997061.issue11266@psf.upfronthosting.co.za>
In-reply-to
Content
When using non-blocking IO, we issue select (or poll,epoll), and after that kernel should guarantee, that recv or send will complete immediatelly, transferring data as needed. But sometimes (as Linux is buggy), such operations results in EINTR error if some signal arrived during this call. In that case python exception generated and typically connection will be closed.
  To recover from this situation it is OK to call recv or send again in case of EINTR. All network functions (recv*, send*, accept, connect) are vulnerable for EINTR in practice.
History
Date User Action Args
2011-03-05 05:09:46socketpairsetrecipients: + socketpair, giampaolo.rodola, segfaulthunter
2011-03-05 05:09:46socketpairsetmessageid: <1299301786.07.0.989325997061.issue11266@psf.upfronthosting.co.za>
2011-03-05 05:09:45socketpairlinkissue11266 messages
2011-03-05 05:09:44socketpaircreate