Issue with bans gr:miner command
UserDC-LeGrand opened this issue · 4 comments
When issuesin the following command: "bans remove gr:xmrig-cpu", it looks like the bans command does not recognize gr as a valid algorithm, which it is. It assumes it's a coin instead....
interesting. You can try 'ghostrider' instead. I will make it so ban is accepted regardless of name, though. This is a bug in that it should be able to accept stat screen naming schemas.
nvm. I figured it out. The ban is not an exclusion.
There are different ways SWARM does bans. If it's user-derived (argument or command), it adds it under "exclusions". This way it is permanent until user removes. (either changing argument at launch, or via the command)
If SWARM implements the ban, the details is added under .\timeout so it can self-manage the ban. The issue here is that bans doesn't do anything with that folder, but it should.
So because of the all the potential combinations- It would take pages of code to try to eliminate every type of specific ban that SWARM does when it activates a "timeout" (adds to .\timeout). It's why I never implemented a means to do so.
The most I'm going to code/allow it to do will be bans remove [algo]:[miner]
-Type, Pool, Coin, and all the other variables users will have to just delete the .\timeout folder to remove the all the bans and start fresh.
And just to note it does says during a benchmark ban it adds its to timeout folder so user is aware that all bans issued from SWARM is in .\timeout