libev-3.48 has just been released

Kandalintsev Alexandre exe at
Thu Oct 30 13:54:41 CET 2008

Do you have any tests showing this problem?
I want to try to wakeup kernel developers.

> If anybody is interested in the gory details of why this was necessary
> with epoll, I can expand the topic in more detail. What prompted the
> change was the realisation that you cannot work around the breakage
> from the child process after a fork, and spurious notifications can be
> generated in cases where they are hard to work around for the  
> application.

More information about the libev mailing list