Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <772ec267ebfcab2d91fe87b53365e352@smtp.hushmail.com>
Date: Wed, 26 Feb 2014 20:01:18 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Status request signallling to children or MPI nodes.

Solar,

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 :-(

magnum

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.