The install.config file contains options for LSF installation and configuration. Use lsfinstall -f install.config to install LSF using the options specified in install.config.
After installation, the install.config containing the options you specified is located in LSF_TOP/8/install/.
Enables dynamically adding and removing hosts. Set the value to "Y" if you want to allow dynamically added hosts.
If you enable dynamic hosts, any host can connect to cluster. To enable security, configure LSF_HOST_ADDR_RANGE in lsf.cluster.cluster_name after installation and restrict the hosts that can connect to your cluster.
Enables backup and rollback for enhancement packs. Set the value to "N" to disable backups when installing enhancement packs (you will not be able to roll back to the previous patch level after installing an EP, but you will still be able to roll back any fixes installed on the new EP).
You may disable backups to speed up install time, to save disk space, or because you have your own methods to back up the cluster.
Required. List of LSF administrators.
The first user account name in the list is the primary LSF administrator. It cannot be the root user account.
Typically this account is named lsfadmin. It owns the LSF configuration files and log files for job events. It also has permission to reconfigure LSF and to control batch jobs submitted by other users. It typically does not have authority to start LSF daemons. Usually, only root has permission to start LSF daemons.
Time in seconds slave LIM waits after startup before calling master LIM to add the slave host dynamically.
This parameter only takes effect if you set ENABLE_DYNAMIC_HOSTS="Y" in this file. If the slave LIM receives the master announcement while it is waiting, it does not call the master LIM to add itself.
Up to 60 seconds for every 1000 hosts in the cluster, for a maximum of 15 minutes. Selecting a smaller value will result in a quicker response time for new hosts at the expense of an increased load on the master LIM.
Full path to the patch backup directory. This parameter is used when you install a new cluster for the first time, and is ignored for all other cases.
The file system containing the patch backup directory must have sufficient disk space to back up your files (approximately 400 MB per binary type if you want to be able to install and roll back one enhancement pack and a few additional fixes). It cannot be the root directory (/).
If the directory already exists, it must be writable by the cluster administrator (lsfadmin).
If you need to change the directory after installation, edit PATCH_BACKUP_DIR in LSF_TOP/patch.conf and move the saved backup files to the new directory manually.
Full path to the patch history directory. This parameter is used when you install a new cluster for the first time, and is ignored for all other cases.
It cannot be the root directory (/). If the directory already exists, it must be writable by lsfadmin.
The location is saved as PATCH_HISTORY_DIR in LSF_TOP/patch.conf. Do not change the directory after installation.