On 05:16 pm, msoul...@digitaltorque.ca wrote:
>On 08/06/10 Itamar Turner-Trauring said:
>>You should probably just use reactor.spawnProcess to fork processes:
>>it
>>implements the process handling for you, and has its own SIGCHLD
>>handler
>>that does the right thing, so you don't have to mainta
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 Tu
On 08/06/10 Itamar Turner-Trauring said:
> You should probably just use reactor.spawnProcess to fork processes: it
> implements the process handling for you, and has its own SIGCHLD handler
> that does the right thing, so you don't have to maintain your own.
The problem is that I'm using the mult
> 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 w
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
