[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110821164019.GA11300@openwall.com>
Date: Sun, 21 Aug 2011 20:40:19 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: MPI / OpenMPI
groszek suggested, assuming that Richard is using MPI:
On Sun, Aug 21, 2011 at 4:22 AM, groszek <necro@...icon.pl> wrote:
> killall -USR1 john
But apparently Richard is using something else:
On Sun, Aug 21, 2011 at 09:52:08AM -0500, Richard Miles wrote:
> Thanks for suggestion, but it doesn't work as expected. It kills my
> current john task and the next on the queue is still not responsive
> with space bar...
>
> ./john.sh: line 21: 14362 User defined signal 1 /tools/jtr/john
> --format=$1 -w:/home/rick/myrockyou-75.txt -rules:$i $2
Richard - you may send all john's a SIGHUP:
killall -HUP john
which makes them update their .rec files right away, then query their
status with:
john --status=SESSION-NAME
This way, you'll see the progress of each of them.
Obviously, this is not very convenient if your only reason to run
multiple john's was to use multiple CPUs. Improvements in this area are
planned. Currently, you can avoid running multiple john's yet use
multiple CPUs for some hash types with an OpenMP-enabled build.
Alexander
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.
