Quote from: doktor83 on July 29, 2019, 04:45:33 AM

Quote from: hesido on July 28, 2019, 09:42:52 PM

Quote from: doktor83 on July 28, 2019, 05:16:47 PM

Quote from: hesido on July 28, 2019, 03:48:44 PM

Quote from: doktor83 on July 28, 2019, 07:14:23 AM

Since then ? I know there is some issue with this when windows changes time (pulls from NTP or user changes clock) - this happens rarely, but other than it should work fine. I will check it.

This thing is for sure, SRB says "1" minute regardless of what setting it is, it may think more / less minutes have passed if there was a clock change (my clock seems fine though), but it specifically says 1 minute still.

Have you tried with 1 's' (--maxnosharesent , not --maxnosharessent like you wrote). Also it's not set in minutes, you set it in seconds.

Ah, I had the option name correct in the command line, but I had no idea it was in seconds!

Code:

--maxnosharesent value (if no share is sent to the pool for x time, restarts miner. def. is 30 min)

Could be changed to:

Code:

--maxnosharesent value (if no share is sent to the pool for x seconds, restarts miner. def. is 1800 seconds (30 min))

Thanks Dok.

Theres a notice on the first page and in the readme that all parameters that take a time value are in seconds

Lol, sure, but as you might have realized from the many questions posed here, that's not how an averagely dumb brain works Cheesy

. I personally skim for the part I need, that's how I probably missed that one. Still, it's good to be explicit Cheesy