LSF Version 7.3 - Platform LSF Configuration Reference

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]"
EGO parameter
EGO_LOCAL_RESOURCES
Default
Not defined
LSF_LOG_MASK
Syntax
LSF_LOG_MASK=message_log_level
Description
Specifies the logging level of error messages for LSF daemons, except LIM, which is controlled
by Platform EGO.
For example:
LSF_LOG_MASK=LOG_DEBUG
If EGO is enabled in the LSF cluster, and EGO_LOG_MASK is not defined, LSF uses the value
of LSF_LOG_MASK for LIM, PIM, and MELIM. EGO vemkd and pem components continue
to use the EGO default values. If EGO_LOG_MASK is defined, and EGO is enabled, then EGO
value is taken.
To specify the logging level of error messages for LSF commands, use
LSF_CMD_LOG_MASK. To specify the logging level of error messages for LSF batch
commands, use LSB_CMD_LOG_MASK.
On UNIX, this is similar to syslog. All messages logged at the specified level or higher are
recorded; lower level messages are discarded. The LSF_LOG_MASK value can be any log
priority symbol that is defined in syslog.h (see syslog).
The log levels in order from highest to lowest are:
lsf.conf
472 Platform LSF Configuration Reference