tar -xzf grouphug-0.1.tar.gz
gh help how
gh help events fits
gh help que
Each node can be started and stopped as you please. They will automatically determine who should be the master. The code to do this is very alpha, so I hope to test and solidify this in the alpha release.
Each node must somehow have a copy of the program. Personally I recommend that each node is accessing the same files via some form of shared storage (be it NFS, GFS, a SAN etc). At the minimum, ghhome/write MUST be accessible as one instance across all nodes. All nodes will need read/write access to this ghhome/write.
Make sure hostname is unique to each node. I can't stress this enough. The hostname is used to identify the node, so if it is not unique multiple nodes will try and handle the same task. FQDN such as node1.example.com should be ok, but is currently untested. Spaces are a big nono (although I have only seen this in Windows environments). Special characters are also not recommented. 16 bit characters have not been tested, so I have no idea what would happen at this point. My suspicion is that if the terminal supports it, it will probably be ok. Feedback and thoughts welcome.