![](https://secure.gravatar.com/avatar/612db31e8d970afe1835950afbbe9ef7.jpg?s=120&d=mm&r=g)
25 May
2007
25 May
'07
4:45 a.m.
A completely wild guess is that forking is confusing PyLucene in a fatal way.
FWIW, I have an application running CherryPy over Twisted, using PyLucene. Since PyLucene isn't thread-safe, every thread must subclass PyLucene.PythonThread, so the underlying "java runtime garbage collector is aware about the python thread upon their creation" (http://lists.osafoundation.org/pipermail/pylucene-dev/2004-June/000037.html). Without this, the apps simply crashes (segfault, see also http://chandlerproject.org/PyLucene/ThreadingInPyLucene). Maybe there's something about that while twistd is daemonizing the process ? Hope that helps. Cheers, Seb -- Sébastien LELONG http://www.sirloon.net sebastien.lelong[at]sirloon.net