Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 26 Feb 2014 20:01:18 +0100
From: magnum <>
Subject: Status request signallling to children or MPI nodes.


Is there a reason you picked SIGUSR2 for fork mode's signalling to 
children instead of SIGUSR1, that the MPI code has used for ages for the 
same thing? I have a patch that changes your code to use SIGUSR1 and 
drops the specific MPI code but I thought you might have had a good 
reason for not doing that?

The main reason I want this is I'm writing a patch that makes John 
reload/process .pot file etc. upon receiving a signal and I realized 
we're out of them :-(


Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ