Platform LSF Reference Version 6.2

bsub
Platform LSF Reference
156
The CPU limit is in the form of [hour:]minute. The minutes can be specified as a number
greater than 59. For example, three and a half hours can either be specified as 3:30, or
210.
The CPU time you specify is the normalized CPU time. This is done so that the job does
approximately the same amount of processing for a given CPU limit, even if it is sent to
host with a faster or slower CPU. Whenever a normalized CPU time is given, the actual
time on the execution host is the specified time multiplied by the CPU factor of the
normalization host then divided by the CPU factor of the execution host.
Optionally, you can supply a host name or a host model name defined in LSF. You must
insert a slash (
/) between the CPU limit and the host name or model name. (See
lsinfo(1) to get host model information.) If a host name or model name is not given,
LSF uses the default CPU time normalization host defined at the queue level
(DEFAULT_HOST_SPEC in
lsb.queues) if it has been configured, otherwise uses
the default CPU time normalization host defined at the cluster level
(DEFAULT_HOST_SPEC in
lsb.params) if it has been configured, otherwise uses
the submission host.
Jobs submitted to a chunk job queue are not chunked if the CPU limit is greater than 30
minutes.
-C core_limit
Sets a per-process (soft) core file size limit for all the processes that belong to this batch
job (see
getrlimit(2)). The core limit is specified in KB.
The behavior of this option depends on platform-specific UNIX systems.
In some cases, the process is sent a SIGXFSZ signal if the job attempts to create a core
file larger than the specified limit. The SIGXFSZ signal normally terminates the process.
In other cases, the writing of the core file terminates at the specified limit.
-D data_limit
Sets a per-process (soft) data segment size limit for each of the processes that belong to
the batch job (see
getrlimit(2)). The data limit is specified in KB. A sbrk call to
extend the data segment beyond the data limit will return an error.
-e err_file
Specify a file path. Appends the standard error output of the job to the specified file.
If the parameter LSB_STDOUT_DIRECT in
lsf.conf is set to Y or y, the standard
error output of a job is written to the file you specify as the job runs. If
LSB_STDOUT_DIRECT is not set, it is written to a temporary file and copied to the
specified file after the job finishes. LSB_STDOUT_DIRECT is not supported on
Windows.
If you use the special character
%J in the name of the error file, then %J is replaced by
the job ID of the job. If you use the special character
%I in the name of the error file,
then
%I is replaced by the index of the job in the array if the job is a member of an array.
Otherwise,
%I is replaced by 0 (zero).
If the current working directory is not accessible on the execution host after the job
starts, LSF writes the standard error output file to
/tmp/.