[issue7978] SocketServer doesn't handle syscall interruption

Vetoshkin Nikita report at bugs.python.org
Tue Nov 9 21:28:39 CET 2010


Vetoshkin Nikita <nikita.vetoshkin at gmail.com> added the comment:

Any news on this? Could we possibly apply patch as is? If I'm not mistaken timeout issue is the only one left unresolved.

About timeout. The most elegant way, would be to use select's syscall timeout parameter, but man 2 select says: "On  Linux,  select()  modifies  timeout to reflect the amount of time not slept; most other implementations do not do this. (POSIX.1-2001 permits either behavior.)  This causes problems both when Linux code which reads timeout is ported to other operating systems, and when code is ported to Linux that reuses a struct timeval for  multiple select()s in a loop without reinitializing it. Consider timeout to be undefined after select() returns."

I'm ready to adapt Yaniv's patch to 2.7

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7978>
_______________________________________


More information about the Python-bugs-list mailing list