Two options: 1. (as Itamar notes) use spawnProcess for all your process spawning needs 2. reactor.run(installSignalHandlers = False) and do your own signal handling
For option #2, you'll almost certainly want to install SIGTERM and SIGINT handlers which call reactor.stop(). Jason On Tue, Jun 8, 2010 at 12:36 PM, Michael P. Soulier < msoul...@digitaltorque.ca> wrote: > Hi, > > I have a twisted service that needs to fork child processes to do tasks, > after > which they will exit. I wrote a signal handler for SIGCHLD but it didn't > seem > to be called. I read something about twisted installing its own signal > handlers that may conflict. Is this true? > > How would you recommend handling a SIGCHLD in twisted? > > Many thanks, > Mike > -- > Michael P. Soulier <msoul...@digitaltorque.ca> > "Any intelligent fool can make things bigger and more complex... It takes a > touch of genius - and a lot of courage to move in the opposite direction." > --Albert Einstein > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkwOcYkACgkQKGqCc1vIvggbUACfY8xqgU2LLOrs0cfR7HngUqmc > LOQAoKkur5+DK8lcZ+q6qWDtjqIpX3Ov > =XM/4 > -----END PGP SIGNATURE----- > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > > -- Jason Rennie Research Scientist, ITA Software 617-714-2645 http://www.itasoftware.com/
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python