Reconnect when algo-perf or algo-min-time have been changed

MoneroOcean / xmrig

Monero (rx/0, rx/wow, rx/loki, defyx, rx/arq, rx/sfx, rx/keva, cn/0, cn/1, cn/2, cn/r, cn/fast, cn/half, cn/xao, cn/rto, cn/rwz, cn/zls, cn/double, cn/gpu, cn-lite/0, cn-lite/1, cn-heavy/0, cn-heavy/tube, cn-heavy/xhv, cn-pico, cn-pico/tlo, argon2/chukwa, argon2/wrkz, astrobwt) CPU/GPU miner

https://moneroocean.stream

GNU General Public License v3.0

275 stars 86 forks source link

Reconnect when algo-perf or algo-min-time have been changed #147

Open Spudz76 opened 5 months ago

Spudz76 commented 5 months ago

When config is reloaded and has changed MO-specific config items that are in the login packet, reconnect. Also add messages about why a reconnect is happening, as an improvement.

Previously, changing algo-perf or algo-min-time would not trigger a reconnection/re-login to update the actual state of things.

Tested:

Spudz76 commented 3 months ago

Updated to honor XMRIG_FEATURE_MO_BENCHMARK so compilation does not fail when disabled.