problem with --runtime

[mastercracker]

Since the trac system is not working right now, I want to check if I am alone with this problem. I got a 6970 and I was testing some of my bruteforce attacks on 5000000 MD5 hashes. In my command line, I have the --runtime 300 switch but it aborts at the wrong time. Last time was around 1 hour and 4 minutes. I will check other attacks that use the --runtime switch and see if it is constant. Anyone has a behavior like this.

[mastercracker]

The time seems to be random, 31 minutes, 37 minutes. I don't know what's going on.

[Rolf]

Try pressing [s] midway and see if that influences anything.

[atom]

please wait for trac coming back and add a ticket then