Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 15 Aug 2015 16:36:45 +0300
From: Solar Designer <>
Subject: Re: --test-full=0 crashes the Bitcoin format

On Sat, Aug 15, 2015 at 09:32:52PM +0800, Kai Zhao wrote:
> Yes, after set OMP_NUM_THREADS=32, the max_keys_per_crypt is 64. But I
> have not reproduced on my laptop after running about 200 times.

How many logical CPUs are available in your VM?

> > Kai, you're currently running two instances of john on super:
> >
> > kai      28475 1159  0.0 2413324 7392 ?        Sl   05:50 7207:40 ./john --test-full=0 --format=bitcoin
> > kai      31899  825  0.0 2413324 7360 ?        Sl   06:29 4806:53 ./john --test-full=0 --format=bitcoin
> >
> > bringing load average to 37.00.  What are these trying to achieve?
> > Suppose one of them or both would crash, would this help in any way?
> Sorry, the two process maybe are zombie process. I did not notice that
> and I just killed them.

Definitely not zombie processes.  When you have time, you might want to
read up on what zombie processes in Unix are.

As to you not noticing yet accumulating two processes, this means that
you're not checking what else is going on on the system before you start
your jobs.  You should.  As a minimum, type "w" before starting a job -
you'd see that there's already load on the system, and you'd need to
check what causes it.


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.