You can get it here.

These instructions are for the current release. Old instructions can be found here. There is now an install script that handels the install. All you need to do is unpack the archive to where you want grouphug to be installed, run the script, then run the tests to create any remaining files. If you need to set special permissions or umask, you should do it before running the tests. If you run it as root it will be installed for everyone. If you run it as a user it will be available to just that user. Although many users may share the same installation.

• Unpack the archive where you want to install grouphug
  

   tar -xzf grouphug-0.1.tar.gz
   cd grouphug-0.1

• Within the unpacked directory, run install-stage1
  

   . ./install-stage1

• Test it
  

  gh test.all

In the distant future, the help system will be ported over to man pages. Until then there is a lot of documentation provided internally.

• How to use help.
  

   gh help how

• How the events system fits together
  

   gh help events fits

• General information about the que system.
  

   gh help que

This section assumes you know how it works.

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.