What to watch out for when running two instances of Hashcat at once?
#9
(01-18-2020, 02:42 AM)royce Wrote: I often run more than one simultaneously, either distributing load among GPUs, or else pausing one long-running job to run a short-running job. This is often easier than quitting and restoring.

The best way to manage this is to assign all running hashcats their own session ID with --session. You can then refer to that session by name when restoring or doing other things.

(Edit: I also use --potfile-path to give them separate potfiles with the same name)

I'm doing this just now, for not very good reasons, and have given separate pot files, separate session files, and taken the --remove off both, as they're hitting the same hash list. It seems to be working OK.
Reply


Messages In This Thread
RE: What to watch out for when running two instances of Hashcat at once? - by blacktraffic - 01-21-2020, 09:43 AM