06-29-2015, 06:59 PM
Hello,
curlyboi, got a question for you.
I have two hashing rigs, running on Ubuntu 14.04 LTS. Rig #1 has 4x Gigabyte R9 280x GPUs, Rig #2 has 4x MSI Twinfrozr III 7950 GPUs.
I use latest version of oclHashcat + Hashtopus.
Hashtopus works great as it should, but I have a problem with "Measuring keyspace..." part when adding new tasks.
Normally, when I start oclHashcat directly without Hashtopus it happens only one time, during first use of that specific dictionary. I assume the result of dictionary stats generation is written on disc and used for next tasks to avoid repeating.
For large dictionaries it takes substantial amount of time to complete, even 30 minutes.
I noticed that every Hashtopus client tries to generate dictionary stats by itself, however when I connect only 1 agent and it finishes "Measuring keyspace" the second agent assigned to task doesn't do that again and starts hashing at sight without generating dictionary stats.
The problem is that when I add another task with the same dictionary, Hashtopus clients generate directory stats again which is a time waste.
Imagine that I have dictionary that is processed within 2 hours, but between each task I have to wait 30 minutes before the hashing starts for dictionary generation of the same file, which is a time and resources waste.
Is there a way to avoid repeated keyspace measurements by Hashtopus?
curlyboi, got a question for you.
I have two hashing rigs, running on Ubuntu 14.04 LTS. Rig #1 has 4x Gigabyte R9 280x GPUs, Rig #2 has 4x MSI Twinfrozr III 7950 GPUs.
I use latest version of oclHashcat + Hashtopus.
Hashtopus works great as it should, but I have a problem with "Measuring keyspace..." part when adding new tasks.
Normally, when I start oclHashcat directly without Hashtopus it happens only one time, during first use of that specific dictionary. I assume the result of dictionary stats generation is written on disc and used for next tasks to avoid repeating.
For large dictionaries it takes substantial amount of time to complete, even 30 minutes.
I noticed that every Hashtopus client tries to generate dictionary stats by itself, however when I connect only 1 agent and it finishes "Measuring keyspace" the second agent assigned to task doesn't do that again and starts hashing at sight without generating dictionary stats.
The problem is that when I add another task with the same dictionary, Hashtopus clients generate directory stats again which is a time waste.
Imagine that I have dictionary that is processed within 2 hours, but between each task I have to wait 30 minutes before the hashing starts for dictionary generation of the same file, which is a time and resources waste.
Is there a way to avoid repeated keyspace measurements by Hashtopus?