[Twisted-Python] twisted threading server has to be stopped with KILL

Itamar Shtull-Trauring itamar at itamarst.org
Tue Feb 8 14:36:04 EST 2005

On Tue, 2005-02-08 at 11:17 -0800, snacktime wrote:
> I have a server that uses threads, and when run standalone or via
> twistd as an application I have to send it a KILL signal if it has
> already answered at least one request.  Or in some cases if I just
> send it an INT it will stop if it's currently handling a lot of
> requests at the time I send it the signal.  Seems like there is
> something I am not doing here that I should be when  using threads?

The system will stop  when all threads are finished, which happens when
they finish their current task. Since that may be blocking (possibly
indefinitely) the program may never exit cleanly. This is a general
problem with blocking calls and not threads, and is not Twisted

More information about the Twisted-Python mailing list