Patch for fork.

[denik]

gevent.fork calls for reinit of libevent in parent process, that leads to strange problems in gevent/libevent after calling fork.

Reported by ABoudkar.

---

earlier comments

ABoudkar said, at 2011-01-27T07:30:40.000Z:

This patch will fix issue 61.

carsten.klein@axn-software.de said, at 2011-03-21T21:06:01.000Z:

AFAIK the original behaviour

1. fork child process
2. if that succeeded, loop.fork()

if ok, but

3. leave it to the user to call loop.reinit()

as is currently implemented seems fine with me. Non Issue?

carsten.klein@axn-software.de said, at 2011-03-21T21:10:25.000Z:

AFAIK the actual problem is calling loop.fork() on the parent process, since that will/may cause libevent to internally fork the loop and all its associated data. perhaps this is what is causing the problem.

so

result = originalfork()
if result == 0:
in child process
loop.fork()
return result

will do the trick?

carsten.klein@axn-software.de said, at 2011-03-21T21:13:12.000Z:

and which is basically what the patch provides - had better read it in full prior posting this :D

Denis.Bilenko said, at 2011-04-28T15:18:00.000Z:

The patch does indeed seem to fix issue #61 when running gevent 0.13.5 on libevent2

Thanks!

Denis.Bilenko said, at 2011-04-28T15:26:26.000Z:

Applied here: https://bitbucket.org/denis/gevent-0.13/changeset/18c7b65aded7

Denis.Bilenko said, at 2011-05-02T10:58:37.000Z:

Issue 61 has been merged into this issue.