Closed nicoschtein closed 10 years ago
i have merged it into a new testing branch, but with the new feature to allow multiple miner software and switching them it will be hard to manage this with smos/bamt because they just use cgminer or now sgminer. when you have a bfgminer for example the mine stop/start will not work. You would need to check the system if it is smos or bamt, then the version of it and finally check to which miner smos is configurated and only if the current running pool use the same miner than you could use the service from bamt/smos. I think this is a bit too much of checking for not soooo much enhancements. I also recognized from another user that stopping the miner normally (for example within the console pressing q) then sometimes the system freezes, instead with killing it it worked.
Make it optional to, instead of running or killing cgminer directly, use the already existing
mine
service:Usage: /etc/init.d/mine {start|stop|restart|reload|force-reload|status}
In
RPCClientApi.class.php
add a check for the optionUse BAMT/SMOS mine service
enabled/disabled and if enabled:kill_cgminer()
should usemine stop
restart_cgminer()
should usemine restart
Will make a PR with smos/bamt code only, for others to test.