LSF_INTERACTIVE_STDERR

Syntax

LSF_INTERACTIVE_STDERR=y | n

Description

Separates stderr from stdout for interactive tasks and interactive batch jobs.

This is useful to redirect output to a file with regular operators instead of the bsub -e err_file and -o out_file options.

This parameter can also be enabled or disabled as an environment variable.
CAUTION:

If you enable this parameter globally in lsf.conf, check any custom scripts that manipulate stderr and stdout.

When this parameter is not defined or set to n, the following are written to stdout on the submission host for interactive tasks and interactive batch jobs:

  • Job standard output messages

  • Job standard error messages

The following are written to stderr on the submission host for interactive tasks and interactive batch jobs:

  • LSF messages

  • NIOS standard messages

  • NIOS debug messages (if LSF_NIOS_DEBUG=1 in lsf.conf)

When this parameter is set to y, the following are written to stdout on the submission host for interactive tasks and interactive batch jobs:

  • Job standard output messages

The following are written to stderr on the submission host:

  • Job standard error messages

  • LSF messages

  • NIOS standard messages

  • NIOS debug messages (if LSF_NIOS_DEBUG=1 in lsf.conf)

Default

Not defined

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 (makefile)

  • bsub pam (HPC features must be enabled)

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

Parent topic: lsf.conf