[ Platform Documentation ]

[ Title ]

[ Contents ]

[ Previous ]

[ Next ]

[ Index ]

---

slave.config

---

Contents

• About slave.config
• Parameters

[ Top ]

---

About slave.config

Dynamically added LSF hosts that will not be master candidates are slave hosts. Each dynamic slave host has its own LSF binaries and local lsf.conf and shell environment scripts (cshrc.lsf and profile.lsf). You must install LSF on each slave host.

The slave.config file contains options for installing and configuring a slave host that can be dynamically added or removed.

Use lsfinstall -s -f slave.config to install LSF using the options specified in slave.config.

Template Location

A template slave.config is located in the installation script directory created when you extract the LSF installation script tar file. Edit the file and uncomment the options you want in the template file. Replace the example values with your own settings to specify the options for your new LSF installation.

---

The sample values in the slave.config template file are examples only. They are not default installation values.

---

Format

Each entry in slave.config has the form:

NAME="STRING1 STRING2 ..."

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

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

Blank lines and lines starting with a pound sign (#) are ignored.

[ Top ]

---

Parameters

• LSF_ADMINS
• LSF_LIM_PORT
• LSF_SERVER_HOSTS
• LSF_TARDIR
• LSF_LOCAL_RESOURCES
• LSF_TOP

LSF_ADMINS

Syntax

LSF_ADMINS="user_name [ user_name ... ]"

Description

Required. Lists the LSF administrators. The first user account name in the list is the primary LSF administrator in lsf.cluster.cluster_name.

The LSF administrator accounts must exist on all hosts in the LSF cluster before installing LSF

The primary LSF administrator account is typically 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. Unless an lsf.sudoers file exists to grant LSF administrators permission, only root has permission to start LSF daemons.

CAUTION

---

You should not configure the root account as the primary LSF administrator.

---

Valid Values

User accounts for LSF administrators must exist on all hosts in the LSF cluster before running lsfinstall.

Example

LSF_ADMINS="lsfadmin user1 user2"

Default

None--required variable

LSF_LIM_PORT

Syntax

LSF_LIM_PORT="port_number"

Description

Optional. TCP service port for slave host to use for communication with the LSF master LIM daemon. Use the same port number as LSF_LIM_PORT in lsf.conf on the master host.

If not specified, the default LSF_LIM_PORT="6879" is used.

Default

Undefined

LSF_SERVER_HOSTS

Syntax

LSF_SERVER_HOSTS="host_name [ host_name ...]"

Description

Optional for shared installation. Required for non-shared installation.

Lists the hosts in the cluster to be set up as LSF server hosts.

Specify a list of host names two ways:

• Host names separated by spaces
• Name of a file containing a list of host names, one host per line.

Valid Values

Any valid LSF host name

Examples

• List of host names:

  LSF_SERVER_HOSTS="hosta hostb hostc hostd"
  

• Host list file:

  LSF_SERVER_HOSTS=:lsf_server_hosts
  

  The file lsf_server_hosts contains a list of hosts:

  hosta
  hostb
  hostc
  hostd
  

Default

The local host where lsfinstall is running

LSF_TARDIR

Syntax

LSF_TARDIR="/path"

Description

Optional. Full path to the directory containing the LSF distribution tar files.

Example

LSF_TARDIR="/usr/local/lsf_distrib"

Default

The parent directory of the current working directory where lsfinstall is running (../current_directory)

LSF_LOCAL_RESOURCES

Syntax

LSF_LOCAL_RESOURCES=resource ...

Description

Optional. Defines instances of local resources residing on the slave host.

• For numeric resources, define name-value pairs:

  [resourcemap value*resource_name]
  

• For Boolean resources, define the resource name in the form:

  [resource resource_name]
  

When the slave host calls the master host to add itself, it also reports its local resources. The local resources to be added must be defined in lsf.shared.

If the same resource is already defined in lsf.shared as default or all, it cannot be added as a local resource. The shared resource overrides the local one.

---

LSF_LOCAL_RESOURCES is usually set in the slave.config file during installation. If LSF_LOCAL_RESOURCES are already defined in a local lsf.conf on the slave host, lsfinstall does not add resources you define in LSF_LOCAL_RESOURCES in slave.config. You should not have duplicate LSF_LOCAL_RESOURCES entries in lsf.conf. If local resources are defined more than once, only the last definition is valid.

---

IMPORTANT

---

Resources must already be mapped to hosts in the ResourceMap section of lsf.cluster.cluster_name. If the ResourceMap section does not exist, local resources are not added.

---

Example

LSF_LOCAL_RESOURCES=[resourcemap 1*verilog] [resource linux]

Default

None--optional variable

LSF_TOP

Syntax

LSF_TOP="/path"

Description

Required. Full path to the top-level LSF installation directory.

Valid value

Must be an absolute path to a local directory on the slave host.

Cannot be the root directory (/).

Recommended value

The file system containing LSF_TOP must have enough disk space for all host types (approximately 300 MB per host type).

Example

LSF_TOP="/usr/local/lsf"

Default

None--required variable

SEE ALSO

lsfinstall(8), install.config(5), lsf.cluster(5), lsf.sudoers(5)

[ Top ]

---

[ Platform Documentation ]

[ Title ]

[ Contents ]

[ Previous ]

[ Next ]

[ Index ]

---

Date Modified: February 24, 2004 Platform Computing: www.platform.com Platform Support: support@platform.com Platform Information Development: doc@platform.com Copyright © 1994-2004 Platform Computing Corporation. All rights reserved.