lsf.conf

The lsf.conf file controls the operation of LSF. The lsf.conf file is created during installation and records all the settings chosen when LSF was installed. The lsf.conf file dictates the location of the specific configuration files and operation of individual servers and applications.

About lsf.conf

The lsf.conf file is used by LSF and applications built on top of it. For example, information in the lsf.conf file is used by LSF daemons and commands to locate other configuration files, executables, and network services. The lsf.conf file is updated, if necessary, when you upgrade to a new version.

This file can also be expanded to include application-specific parameters.

Parameters in this file can also be set as environment variables, except for the parameters related to job packs.

If you have installed LSF in a mixed Windows and UNIX or Linux cluster, you must make sure that lsf.conf parameters set on UNIX and Linux match any corresponding parameters in the local lsf.conf files on your Windows hosts.

Corresponding parameters in ego.conf

When EGO is enabled in LSF, you can configure some LSF parameters in the lsf.conf file that have corresponding EGO parameter names in EGO_CONFDIR/ego.conf (LSF_CONFDIR/lsf.conf is a separate file from EGO_CONFDIR/ego.conf). If both the LSF and the EGO parameters are set in their respective files, the definition in ego.conf is used. You must continue to set LSF parameters only in lsf.conf.

When EGO is enabled in the LSF cluster (LSF_ENABLE_EGO=Y), you also can set the following EGO parameters related to LIM, PIM, and ELIM in either lsf.conf or ego.conf:
  • EGO_DISABLE_UNRESOLVABLE_HOST (dynamically added hosts only)
  • EGO_ENABLE_AUTO_DAEMON_SHUTDOWN
  • EGO_DAEMONS_CPUS
  • EGO_DEFINE_NCPUS
  • EGO_SLAVE_CTRL_REMOTE_HOST
  • EGO_WORKDIR
  • EGO_PIM_SWAP_REPORT
  • EGO_ESLIM_TIMEOUT

If EGO is not enabled, you do not need to set these parameters.

After you change lsf.conf configuration

Depending on which parameters you change, you might need to run one or more of the following commands after you change parameters in the lsf.conf file:
  • lsadmin reconfig to reconfigure LIM
  • badmin reconfig to reconfigure mbatchd without restarting
  • badmin mbdrestart to restart mbatchd
  • bctrld restart sbd to restart sbatchd
Note: Most parameters require only reconfiguration (lsadmin reconfig or badmin reconfig). Several LSF parameters require you to restart mbatchd (badmin mbdrestart). Parameters that require restart are indicated in the parameter description.

Location

The default location of the lsf.conf file is in the $LSF_TOP/conf directory. This default location can be overridden when necessary by either the environment variable LSF_ENVDIR.

Format

Each entry in lsf.conf has one of the following forms:
NAME=VALUE
NAME=
NAME="STRING1 STRING2 ..."

The equal sign = must follow each NAME even if no value follows and there should be no space beside the equal sign.

A value that contains multiple strings separated by spaces must be enclosed in quotation marks.

Lines starting with a pound sign (#) are comments and are ignored. Do not use #if as this is reserved syntax for time-based configuration.
Tip: Starting in Fix Pack 13, the default values of the following three parameters are changed to:
LSF_GPU_AUTOCONFIG=Y
LSB_GPU_NEW_SYNTAX=extend
LSF_GPU_RESOURCE_IGNORE=Y

If you have Fix Pack 13 installed, no further action is needed to set these parameters. If you have Fix Pack 12 or earlier, consider explicitly configuring the same values to these three parameters.

If you want to keep the former GPU behavior, and any one of the three parameters are missing in lsf.conf file, you must explicitly configure the following default settings that are defined in Fix Pack 12 or earlier:
LSF_GPU_AUTOCONFIG=N
LSB_GPU_NEW_SYNTAX=N
LSF_GPU_RESOURCE_IGNORE=N