[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU159-W453B42267457B72BF2369AA4870@phx.gbl>
Date: Fri, 20 Jan 2012 19:54:55 +0000
From: Alex Sicamiotis <alekshs@...mail.com>
To: <john-users@...ts.openwall.com>
Subject: OpenMP progress report bug with multiple 1 thread instances
I'm running two instances of OpenMP john 1.7.9 (non jumbo) for DES cracking from two different directories, cracking with different rulesets... I'm using
export OMP_NUM_THREADS=1
...for both shells, as I have a dual core cpu and each one is assigned to one instance (priority -10 for the first and 19 for the second).
Now...
This is the second instance that I started running a few hours ago
linux-1mo8:/johnrun/49/3 # ./john-openMP-mssse3-fast-core2-icc -restore
Loaded 2507 password hashes with 1862 different salts (Traditional DES [128/128 BS SSE2-16])
Remaining 920 password hashes with 831 different salts
guesses: 0 time: 0:00:09:02 0% c/s: 2771K trying: aagg7223 - aagh1318
guesses: 0 time: 0:00:09:07 0% c/s: 2783K trying: aagj1799 - aagj5894
guesses: 0 time: 0:00:09:08 0% c/s: 2786K trying: aagj5895 - aagj9980
guesses: 0 time: 0:02:29:47 0% c/s: 3457K trying: aezw8535 - aezx2620
guesses: 0 time: 0:03:28:00 1% c/s: 3494K trying: ahah5927 - ahah9022
guesses: 0 time: 0:03:28:15 1% c/s: 3494K trying: ahao1463 - ahao5558
guesses: 0 time: 0:04:25:23 1% c/s: 3543K trying: ajbw6423 - ajbw0518
...and this is the first instance which is running for two days
linux-1mo8:/johnrun/49/2 # ./john-openMP-mssse3-fast-core2-icc -restore
Loaded 2507 password hashes with 1862 different salts (Traditional DES [128/128 BS SSE2-16])
Remaining 920 password hashes with 831 different salts
guesses: 5 time: 1:19:37:02 15% c/s: 4083K trying: kfx13511 - kfx17506
guesses: 5 time: 2:00:49:26 20% c/s: 4121K trying: los47399 - los51494
guesses: 5 time: 2:01:32:59 21% c/s: 4126K trying: lto75367 - lto79462
guesses: 5 time: 2:01:58:47 22% c/s: 4129K trying: lwl46471 - lwl40566
guesses: 5 time: 2:02:30:57 22% c/s: 4131K trying: lzz82951 - lzz86046
guesses: 5 time: 2:04:30:07 24% c/s: 4143K trying: mnh44999 - mnh48094
guesses: 5 time: 2:05:04:42 25% c/s: 4146K trying: mrc69507 - mrc73602
guesses: 5 time: 2:05:05:04 25% c/s: 4146K trying: mrd75003 - mrd70198
guesses: 5 time: 2:06:03:16 0% c/s: 4151K trying: mxq14759 - mxq18854
guesses: 5 time: 2:06:03:21 0% c/s: 4151K trying: mxq39335 - mxq43420
guesses: 5 time: 2:06:03:34 0% c/s: 4151K trying: mxq90775 - mxq04860
guesses: 5 time: 2:06:19:15 1% c/s: 4153K trying: mzk63719 - mzk67814
guesses: 5 time: 2:06:19:23 1% c/s: 4153K trying: mzk04679 - mzk08774
guesses: 5 time: 2:07:00:35 1% c/s: 4157K trying: nea09055 - neb14140
guesses: 5 time: 2:07:02:39 1% c/s: 4157K trying: neh10359 - neh24454
...so it seems that, at the exact point of time when the second instance started (a few hours ago), the first instance got a reset in its progress report to 0% - but continued cracking ok. The 2 instances are running from separate directories so no interaction between them.It seems like a trivial / minor bug, but thought to report it anyway.
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.
