[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4255c2570808171215s57539166j9810764eaf3eb8e7@mail.gmail.com>
Date: Sun, 17 Aug 2008 13:15:13 -0600
From: RB <aoz.syn@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: jtr and openmpi 1.2.3
On Sat, Aug 16, 2008 at 3:39 PM, Murat D. Kadirov <banderols@...il.com> wrote:
> 01:50 Sun 17 Aug, Murat D. Kadirov wrote:
>> I try to compile jtr together with openmpi 1.2.3. I compile last
>> release from http://www.openwall.com/john/, with patch from
>> http://www.bindshell.net/tools/johntheripper and openmpi 1.2.3. I run
>> 'john shadow' and in terminal top, and I see that from four only one
>> kernel works for me (I have Core 2 Quad Q6600). What I am doing wrong
>> and how I can make, that all four kernels worked?
>
> I tried pre patched version john-1.7.3.1-mpi8.tar.gz from
> http://www.bindshell.net/tools/johntheripper. The same result. Run:
>
> murat[run]$ mpirun -np 4 ./john shadow
>
> Occurs nothing. When stop (Ctrl^C) I get errors:
The problem is that the MPI patches expect the end user to be at least
marginally familiar with running an MPI environment. That said, the
most likely explanation is that you failed to initialize your MPI
environment by running 'mpd' before using 'mpirun' - mpd is the
traditional MPI management daemon and has to be running before you'll
get anything going.
This is far more MPI-specific than JtR-specific, but I suppose it
ought to be added to the parallelization page anyway, since it (and
Gentoo's recent addition of the 'mpi' USE keyword) are likely to bring
in a bunch of MPI-inexperienced users. They also insisted on openmpi
instead of mpich2, since the developer responsible had a bad
experience in interop between PPC and x86 machines on mpich2. *sigh*
--
To unsubscribe, e-mail john-users-unsubscribe@...ts.openwall.com and reply
to the automated confirmation request that will be sent to you.
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.
