What to watch out for when running two instances of Hashcat at once?
#4
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)
~
Reply


Messages In This Thread
RE: What to watch out for when running two instances of Hashcat at once? - by royce - 01-18-2020, 02:42 AM