Quote from: chipless on May 13, 2019, 08:52:56 AM

Quote from: efudd on May 13, 2019, 03:34:29 AM

Since the dev pool stay in place even when not being used, if the primary pools are not reachable or otherwise have some connectivity issue, cgminer will automatically fail over to another pool. There is a chance in that scenario that it could make it to the dev pool.

However, when the primary pool recovers, cgminer should automatically switch back within 5 minutes of identifying the pool as responsive again (it has a 5 minute holdback timer to make sure things stabilize).

This scenario could be what you have seen. There should be clear indication in the logs if this were the case.

Regardless, please do let me know if you isolate things any more. I am definitely interested in ensuring everything acts as expected.

Thank you,

Jason

Hmm. How convenient...was that another mistake to mine for you if they cant reach their own server rather then let it go idle and save the power. WOW....That sounds like a Bitmain trick. Something else you ust forgot to tell your users. Whats that now about 5 or 6 things that were in your releases that you just forgot to mention. Sounds like some of your users need a refund to pay for that extra electric you used from them

Lol. Yeah, default cgminer behavior; itll go to an alive pool. Equal probability by default of going to any other configured pool.

EDIT: also, default cgminer behavior when network is down is to ramp fans to 100% and power is not shut off.... so by default it eats power doing nothing. You do not understand the product and tooling you are working with at all.

-j