Quote from: bathrobehero on January 28, 2014, 08:28:25 PM

Quote from: Prima Primat on January 28, 2014, 07:17:23 PM

Sooo Christian, I don't want to be pushy, but any progress on that next version? Wink

Specifically I'm interested in a failover option.

In my opinion failover at this stage is kind of a luxury, but the simplest way to do it was to set cudaMiner to exit if it crashes instead of getting stuck in a loop and spamming the screen (counting the number of total errors and if that number reaches X in the last Y seconds, exit) so you could use a batch file where you could just list all the failovers you want.

I was thinking about this - specifically for Linux - at the moment I am trying to cobble something together using swatch to monitor the output of cudaminer - configure swatch to take an action on seeing n amount of say "disconnect" or "timeout" and killing the current cudaminer before restarting on the next pool configured. In theory it should be fairly straightforward but I'm not having any joy with swatch in its "--read-pipe" mode, it doesn't seem to spot even the most simple of things. If I get it figured I'll post it up here.