fireice-uk / xmr-stak

Free Monero RandomX Miner and unified CryptoNight miner
GNU General Public License v3.0
4.05k stars 1.79k forks source link

command line to reduce pool connect retries for multi-algo mining #596

Closed Angel996 closed 6 years ago

Angel996 commented 6 years ago

Please add a command line option to stop xmr-stak from forever reconnecting to pool. This ruins multi-algo mining (e.g. miningpoolhub.com: whenever pool wants to switch algos, it drops/refuses connection and skips to next miner/algo). All miners have this option. The params in question are _calltimeout, _retrytime and _giveuplimit. _Giveuplimit alone would suffice.

Using config.txt for this creates a lot of confusion (new pool address overwritten by command line, yet miner trying to connect to previous pool found in config.txt (the so-called "background connecting") etc etc)

Thank you very much indeed!

p.s. Please see, etn-eu2.nanopool.org specified on command line, yet, miner attempts to connect to europe.cryptonight-hub.miningpoolhub.com which is in config.txt

[2017-12-18 13:07:30] : Start mining: MONERO
[..........]
[2017-12-18 13:07:30] : hwloc: memory pinned
[[2017-12-18 13:07:30] : Fast-connecting to europe.cryptonight-hub.miningpoolhub.com:12024 pool ...
[2017-12-18 13:07:30] : Fast-connecting to etn-eu2.nanopool.org:13433 pool ...
[2017-12-18 13:07:30] : TLS fingerprint [etn-eu2.nanopool.org:13433] SHA256..........=
[2017-12-18 13:07:30] : Pool etn-eu2.nanopool.org:13433 connected. Logging in...
[2017-12-18 13:07:30] : Pool europe.cryptonight-hub.miningpoolhub.com:12024 connected. Logging in...
[2017-12-18 13:07:30] : SOCKET ERROR - [europe.cryptonight-hub.miningpoolhub.com:12024] invalid username used for login
[2017-12-18 13:07:30] : SOCKET ERROR - [europe.cryptonight-hub.miningpoolhub.com:12024] RECEIVE error: socket closed
[2017-12-18 13:07:30] : Difficulty changed. Now: 120001.
[2017-12-18 13:07:30] : Pool logged in.
fireice-uk commented 6 years ago

Please read config.txt

Angel996 commented 6 years ago

You didn't read my post at all. I don't want to use config.txt, since it creates a lot of confusion when mining for multiple pools. You are forcing users to use config.txt ONLY to utilize this option. I had to create a bash script that creates a custom config.txt on every miner run to go around this. Does this make sense? I think not.

Using config.txt for this creates a lot of confusion (new pool address overwritten by command line, yet miner trying to connect to previous pool found in config.txt (the so-called "background connecting") etc etc)