v0.5.3 was closing itself(?) occasionally, I assume it was losing connection to the pool and running out of reconnect attempts. I'm testing 0.5.5 now to see if the problem still exists without the reconnect attempt limit. Should really use the log I suppose.
lol sample.bat
echo Don't forget to change your pool and login information. :1 zm --server eu1-zcash.flypool.org --port 3333 --user t1user.rig --dev 0 --time goto 1
Can I ask about "new" feature ? May be i'm fool and didn't see it, existing already - total amount of shares found by card and by rig GPU0 80C Sol/s: 310.3 Sol/W: 2.50 Avg: 286.7 I/s: 165.1 Sh: 1.17 1.00 47 there is no "total" amount as I understand ... P.S. edit first message and add pls approx speed's for 1060-3, 1060-6 , 106, and so on cards. Tnx ! add: --temp-target for each card or one for all ? for each doesn't working under unix
"good" miner, w/o any correct statistic. I'm not sure, that you all, receiving on display what you have in reallity
after 1 GPU halted by overclock error, miner still show "total" as earler. and doesn't show any erorrs.. it's really, not a good
Since one of your GPUs crashed it stopped updating it's stats, there is no infrastructure to detect such situations currently so total numbers were still using the old values of the crashed GPU.
I wasn't aware so many of you are using overclocked/unstable systems, however I'm currently working on an GPU responsiveness infrastructure - so this kind of things will improve.
since GPU not updating their stats, and send to hashed - you as i understand, can detect that GPU was crashed and remove it from overall stst, because many watchdogs tuned to overall stats...