[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d2a3170c5adccdd65fa3e1823e63077@smtp.hushmail.com>
Date: Tue, 05 Aug 2014 01:31:04 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Splitting workload on multiple hosts
On 2014-08-04 16:44, Rich Rumble wrote:
> On Mon, Aug 4, 2014 at 5:50 AM, magnum <john.magnum@...hmail.com> wrote:
>> Basically the syntax for MPI with --node is the same as for --fork with
>> --node. So these two examples are equivalent in terms of work space:
>>
>> ./john -fork=16 -node=1-16/10000 (...)
>>
>> mpirun -host=alpha,bravo -np 16 ./john -node=1-16/10000 (...)
>>
> Since Fork is no good for Windows and i currently want to dumbforce
> something. I don't have network connectivity to most of the hosts I'm
> pooling, so I may have to go and use live CD's and use Fork after all, but
> in linux. I am using node like the example, but I'm not sure it will work
> on external modes as well as fork would.
The key space distribution is 100% identical whether you use fork, MPI
or just manual instances of --node.
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.
