LSF Version 7.3 - Platform LSF Configuration Reference

Note:
The path name for the post-execution command must be an
absolute path. Do not define POST_EXEC=
$USER_POSTEXEC when
LSB_PRE_POST_EXEC_USER=root.
For Windows:
•
The pre- and post-execution commands run under cmd.exe /c
•
The standard input, standard output, and standard error are set to NULL
•
The PATH is determined by the setup of the LSF Service
Note:
For post-execution commands that execute on a Windows Server
2003, x64 Edition platform, users must have read and execute
privileges for cmd.exe.
Default
Not defined. No post-execution commands are associated with the queue.
PRE_EXEC
Syntax
PRE_EXEC=command
Description
Enables pre-execution processing at the queue level. The PRE_EXEC command runs on the
execution host before the job starts. If the PRE_EXEC command exits with a non-zero exit
code, LSF requeues the job to the front of the queue.
Pre-execution commands can be configured at the queue, application, and job levels and run
in the following order:
1.
The queue-level command
2.
The application-level or job-level command. If you specify a command at both the
application and job levels, the job-level command overrides the application-level
command; the application-level command is ignored.
The PRE_EXEC command uses the same environment variable values as the job, and runs
under the user account of the user who submits the job. To run pre-execution commands
under a different user account (such as root for privileged operations), configure the parameter
LSB_PRE_POST_EXEC_USER in lsf.sudoers.
For UNIX:
•
The pre- and post-execution commands run in the /tmp directory under /bin/sh -c,
which allows the use of shell features in the commands. The following example shows valid
configuration lines:
PRE_EXEC= /usr/share/lsf/misc/testq_pre >> /tmp/pre.out
POST_EXEC= /usr/share/lsf/misc/testq_post | grep -v "Hey!"
•
LSF sets the PATH environment variable to
PATH='/bin /usr/bin /sbin /usr/sbin'
lsb.queues
Platform LSF Configuration Reference 307