[Twisted-Python] epoll keep sharing state between process even after fork.
Phil Mayers
p.mayers at imperial.ac.uk
Wed Oct 23 10:50:36 MDT 2013
On 23/10/13 17:39, Phil Mayers wrote:
> 2. Arrange for the epoll object (or FD) to be closed after fork, but
> before exec, so that the child process can't fiddle with it
See also:
http://bugs.python.org/issue8713
...which suggests Python 3.4 added fork+exec support to multiprocessing.
On Unix and older Python versions, you're stuck with plain fork and all
the attendant horribleness.
This is a multiprocessing bug IMHO.
More information about the Twisted-Python
mailing list