their coin forked again. I'm not sure yet if I'll ever bring it back.
Why is it that whenever you remove or disable an algo, the miners do not fail over to another algo? I have a script written out like how you suggest in the site, but when it fails the m7m, it would try xevan next, but then gets disconnected, then yescrypt, but then gets disconnected, then goes back to m7m (which fails), and repeats itself.
[2017-08-21 09:23:57] Starting Stratum on stratum+tcp://mine.zpool.ca:3739
[2017-08-21 09:23:57] 8 miner threads started, using 'xevan' algorithm.
[2017-08-21 09:23:58] stratum_recv_line failed
[2017-08-21 09:23:58] ...terminating workio thread
[2017-08-21 09:23:58] workio thread dead, exiting.
[2017-08-21 09:24:13] Starting Stratum on stratum+tcp://mine.zpool.ca:6033
[2017-08-21 09:24:13] 8 miner threads started, using 'm7m' algorithm.
[2017-08-21 09:24:14] Stratum connection failed: Failed to connect to mine.zpool.ca port 6033: Connection refused
[2017-08-21 09:24:14] ...terminating workio thread
[2017-08-21 09:24:14] workio thread dead, exiting.
[2017-08-21 09:24:24] Starting Stratum on stratum+tcp://mine.zpool.ca:6233
[2017-08-21 09:24:24] 8 miner threads started, using 'yescrypt' algorithm.
[2017-08-21 09:24:26] stratum_recv_line failed
[2017-08-21 09:24:26] ...terminating workio thread
[2017-08-21 09:24:26] workio thread dead, exiting.
Shouldn't it fail m7m, then start mining the next profitable coin (in this case, xevan)?