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.
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.
By default, only root can start, stop, or restart the cluster.
This step gives egoadmin (the cluster administrator) permission to do these things also.
When you run egosetsudoers.sh, it does the following:
It creates the /etc/ego.sudoers file. The file owner is
rootand the permissions are set to
600because 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.
Log on as egoadmin (the cluster administrator account you made during installation) and take the following steps:
If you cannot use the default installation directory, choose any directory on your host as the installation directory. The installer will create the directory if it does not already exist. If it already exists, make sure it is empty.
Read this section, then return to the default procedure (Define the cluster administrator). However, when it is time to run the RPM package, install to a custom directory using these instructions instead of the default instructions.
To find out which version of RPM you are using, use the rpm --version option. Different versions of RPM require different options to install the packages.
If you have RPM version 4.1.x or earlier: Some versions of RPM do not support the --prefix option. If the --prefix option is not supported, you need to set the RPM_INSTALL_PREFIX variable and specify the installation directory you want. This is just like setting the DERBY_DB_HOST variable; use one of the methods described in Define the database host.
For RPM version 4.1.x or earlier, if the --prefix option is not supported, set one more environment variable before you run the package:
The installer will create the installation directory if it does not already exist.