Author martius
Recipients gvanrossum, martius, vstinner, yselivanov
Date 2014-12-01.09:23:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417425786.04.0.0696534583373.issue21998@psf.upfronthosting.co.za>
In-reply-to
Content
Guido,

Currently in my program, I manually remove and then re-adds the reader to the loop in the parent process right after the fork(). I also considered a dirty monkey-patching of remove_reader() and remove_writer() which would act as the original versions but without removing the fds from the epoll object (ensuring I don't get bitten by the same behavior for an other fd).

The easiest fix, I think, is indeed to close the selector without unregistering the fds, but I don't know if doing so would have undesired side effects on an other platform than Linux (resources leak, or the close call failing maybe).
History
Date User Action Args
2014-12-01 09:23:06martiussetrecipients: + martius, gvanrossum, vstinner, yselivanov
2014-12-01 09:23:06martiussetmessageid: <1417425786.04.0.0696534583373.issue21998@psf.upfronthosting.co.za>
2014-12-01 09:23:06martiuslinkissue21998 messages
2014-12-01 09:23:05martiuscreate