LSF Version 7.3 - Platform LSF Configuration Reference

Notes
When this parameter is set, the change affects interactive tasks and interactive batch jobs run
with the following commands:
•
bsub -I
•
bsub -Ip
•
bsub -Is
•
lsrun
•
lsgrun
•
lsmake (Platform LSF Make)
•
bsub pam (Platform LSF HPC)
Limitations
•
Pseudo-terminal: Do not use this parameter if your application depends on stderr as a
terminal. This is because LSF must use a non-pseudo-terminal connection to separate
stderr from stdout.
•
Synchronization: Do not use this parameter if you depend on messages in stderr and
stdout to be synchronized and jobs in your environment are continuously submitted. A
continuous stream of messages causes stderr and stdout to not be synchronized. This
can be emphasized with parallel jobs. This situation is similar to that of rsh.
•
NIOS standard and debug messages: NIOS standard messages, and debug messages (when
LSF_NIOS_DEBUG=1 in lsf.conf or as an environment variable) are written to
stderr. NIOS standard messages are in the format <<message>>, which makes it easier
to remove them if you wish. To redirect NIOS debug messages to a file, define
LSF_CMD_LOGDIR in lsf.conf or as an environment variable.
See also
LSF_NIOS_DEBUG, LSF_CMD_LOGDIR
LSF_LD_SECURITY
Syntax
LSF_LD_SECURITY=y | n
Description
LSF_LD_SECURITY: When set, jobs submitted using bsub -Is or bsub -Ip cause the
environment variables LD_PRELOAD and LD_LIBRARY_PATH to be removed from the job
environment during job initialization to ensure enhanced security against users obtaining root
privileges.
Two new environment variables are created (LSF_LD_LIBRARY_PATH and
LSF_LD_PRELOAD) to allow LD_PRELOAD and LD_LIBRARY_PATH to be put back
before the job runs.
Default
N
lsf.conf
464 Platform LSF Configuration Reference