Customize the cluster properties at installation by setting variables to specify the cluster administrator, the cluster name, and the base connection port.
Set custom variables before installation if you wish to customize the cluster properties.
You can set environment variables according to your login shell. If you do not wish to use environment variables, create a simple text file /tmp/install.config and enter each variable on a new line. An environment variable is ignored if the same variable is set in the cluster properties configuration file.
For RPM version 4.2.x or later and all versions of RPM which support the --prefix option:
rpm -ivh --prefix /opt/test/ egocomputehost-linux2.4-glibc2.3-x86-1.2.3-nnnnnn.rpm
For RPM version 4.1.x or earlier, if --prefix is not supported, set one more environment variable before you run the package:
setenv RPM_INSTALL_PREFIX install_dir
setenv RPM_INSTALL_PREFIX /opt/test/
rpm -ivh egocomputehost-linux2.4-glibc2.3-x86-1.2.3-nnnnnn.rpm
The installer will create the installation directory if it does not already exist.
On Linux hosts, set the environment before you run any EGO commands. You need to do this once for each session you open. Both root and egoadmin accounts use EGO commands to configure and start the cluster.
You need to reset the environment if the environment changes during your session, for example, if you run egoconfig mghost, which changes the location of some configuration files.
These examples assume the default installation directory /opt/ego.
Optional. A root user within a Linux environment can choose to give root privileges within the cluster to the cluster administrator.
By default, only root can start, stop, or restart the cluster.
Give root privileges to egoadmin so that egoadmin can start a local host in the cluster, or shut down or restart any hosts in the cluster from the local host. For egoadmin or root to start the cluster, or start any hosts specified by name, you need to be able to run rsh across all hosts in the cluster without having to enter a password; see your operating system documentation for information about configuring rsh.
Do the following to give root privileges to egoadmin for one host. Run the command on each host in the cluster.
When you run egosetsudoers.sh, it does the following:
It creates the /etc/ego.sudoers file. The file owner is root and the permissions are set to 600 because you ran this command as root. Only the root user can edit this file.
It will setuid the egosh command and change the owner of egosh to root.
Whenever you see instructions to log on as root to start, stop, or restart a host in the cluster, you may log on as egoadmin instead.
On Linux hosts, set the environment before you run any EGO commands. You need to do this once for each session you open. Both root and egoadmin accounts use EGO commands to configure and start the cluster.
You need to reset the environment if the environment changes during your session, for example, if you run egoconfig mghost, which changes the location of some configuration files.
These examples assume the default installation directory /opt/ego.
Look for the host you added in the list of the resources.
If you can see the host name in the list of resources, that host was successfully added to the cluster.
This test detects hosts even if the host is not currently available. Some hosts make take a while to become available after they are added to the cluster.