[issue1540386] SocketServer.ForkingMixIn.collect_children() waits on pid 0

Changes by Terry J. Reedy : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue1540386] SocketServer.ForkingMixIn.collect_children() waits on pid 0

Jeffrey Yasskin added the comment: Yes, sorry. That was fixed in r69927. -- ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue1540386] SocketServer.ForkingMixIn.collect_children() waits on pid 0

Stefan Ring added the comment: Jeffrey, this very commit broke it. See also issue 5814. The same happened for me last week. What makes it especially bad is that even once enough children terminate, the SocketServer won't be able to handle any more connections; it just throws this Exception again

[issue1540386] SocketServer.ForkingMixIn.collect_children() waits on pid 0

Changes by Ralf Schmitt <[EMAIL PROTECTED]>: -- nosy: +schmir _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsu

[issue1540386] SocketServer.ForkingMixIn.collect_children() waits on pid 0

Jeffrey Yasskin added the comment: Mostly fixed in r61106. This should make the buildbots happy, but there is still a corner case in which we waitpid(0) and could confuse other libraries. -- nosy: +jyasskin type: -> behavior versions: +Python 2.6 _ T