Multi-Machine support release!
Update r636e now available!
- Not everything is done that I wanted, but multi-machine support is in!
- All communications are securely tunneled through SSH via uniquely generated keys (every installation has their own unique public/private keys generated)
- Added a 'Log' tab to the smartcoin screen session which tails the smartcoin.log to make it easier to see whats going on
- If you are running a custom lockup.sh script, the machine number firing the lockup is passed as the first parameter so you can alert yourself of which machine caused the problem, take different actions based on machine number, etc...
KNOWN ISSUES WITH MULTI-MACHINE SUPPORT:
- during auto detection run, the updatedb command fails. I'd recommend running it yourself on the remote machine before hand
- If a remote machine normally runs smartcoin as root (with sudo - Linuxcoin would be an example of this), then when setting up a remote machine from Configure Machines, you must use the username 'root'. This also means that the remote machine must have a root password for this to work. To set up a root password, on the remote machine (before setting up the machine entry on the control screen):
then enter a password twice. You can now set up the remote machine in Smartcoin using the 'root' user
- When editing a machine, you can select to disable it. The disabled flag DOES work, however a restart of smartcoin is required to see the disabled flag (I.e. if 'Machine#3' is running, and you go to Edit Machines and change its disabled flag to yes, then the status display for screen #3 will stay there until a restart of smartcoin is performed.
- Things aren't yet optimized on the multi-machine side of things, and a lot of live database queries are going on. This isn't an issue, but may show as a little extra CPU usage and or slow refreshes on the remote machines. Optimizations to this part of the code will happen once I see how it works for everyone.
- detected phoenix installations on remote machines default to poclbm kernel. You can Configure Miners->Edit for the machine, and change it manually to phatk if you want (will work on fixing soon)
- cgminer autodetection isn't working currently, but you can always add the entry manually for now.
- The multi-machine functionality was made with local LAN networks in mind, but it will work with a host across the internet - just don't expect blazing refresh speeds if you use a remote host across the internet.
- The <<<FAILED>>> status message is disabled for now until I can make a multi-machine safe way to determine if a miner session launched successfully or not
A BIG BIG BIG thanks to EnzoMatrix, krzynek1 and plantucha for allowing me remote access to their machines. I did some test on all of these machines and everything appears to be working. I did my best to keep their downtime to a bare minimum
Please give it a try, and report your problems or successes. The sooner we verify how things work on different installations, the sooner I can get to optimizing and fixing the newest problems.