| [ Platform Documentation ] | [ Title ] | [ Contents ] | [ Previous ] | [ Next ] | [ Index ] |
lsrun
runs an interactive task through LSF
SYNOPSIS
lsrun [-l] [-P] [-S] [-v] [-m "host_name ..." | -m "cluster_name ..."]
[-R "res_req"] command [argument ...]
lsrun [-h | -V]
DESCRIPTION
Submits a task to LSF for execution.
With MultiCluster job forwarding model, the default is to run the task on a host in the local cluster.
By default, lsrun first tries to obtain resource requirement information from
the remote task list to find an eligible host. (See lseligible(1) and
ls_task(3).) Otherwise, lsrun runs the task on a host that is of the same host
type (or architecture) as the submission host. If several hosts of the same
architecture are available, the host with the lowest CPU and memory load is
selected.
By default, if execution fails and the local host satisfies resource requirements, LSF runs the task locally.
By default, lsrun does not create a pseudo-terminal when running the task.
OPTIONS
-l
If execution on another host fails, runs the task locally.
-L
Forces lsrun to go through RES to execute a task. By default, lsrun will not
use RES if the task is going to run on the current host.
-P
Creates a pseudo-terminal when starting the task on UNIX hosts. This is
necessary in order to run programs that require a pseudo-terminal (for
example, vi).
This option is not supported on Windows.
-S
Creates a pseudo-terminal with shell mode support when starting the task on
a UNIX host. Shell mode support is required for running interactive shells or
applications which redefine the CTRL-C and CTRL-Z keys (for example, jove).
This option is not supported on Windows.
-v
Displays the name of the host running the task.
-m "host_name ..." | -m "cluster_name ..."
The execution host must be one of the specified hosts. If a single host is specified, all resource requirements are ignored.
If multiple hosts are specified and you do not use the -R option, the execution
host must satisfy the resource requirements in the remote task list (see
lsrtasks(1)). If none of the specified hosts satisfy the resource requirements,
the task will not run.
With MultiCluster job forwarding model, the execution host can be a host in
one of the specified clusters, if the remote cluster accepts tasks from the local
cluster. (See RemoteClusters section in lsf.cluster(5).)
-R "res_req"
Runs the task on a host that meets the specified resource requirement. The size
of the resource requirement string is limited to 512 bytes. For a complete
explanation of resource requirement expressions, see lsfintro(1). To find
out what resources are configured in your system, use lsinfo(1) and
lshosts(1).
LSF supports ordering of resource requirements on all load indices, including external load indices, either static or dynamic.
If the -m option is specified with a single host name, the -R option is ignored.
-h
Prints command usage to stderr and exits.
-V
Prints LSF release version to stderr and exits.
USAGE
You can use lsrun together with other utility commands such as lsplace(1),
lsload(1), lsloadadj(1), and lseligible(1) to write load sharing
applications in the form of UNIX shell scripts.
lsrun supports interactive job control. Suspending lsrun suspends both the
task and lsrun, and continuing lsrun continues the task.
The -n option of rsh(1) can be simulated by redirecting input from
/dev/null. For example:
lsrun cat </dev/null &
SEE ALSO
rsh(1), lsfintro(1), ls_rexecv(3), lsplace(1), lseligible(1),
lsload(1), lshosts(1), lsrtasks(1), lsf.cluster(5)
DIAGNOSTICS
lsrun exits with status -10 and prints an error message to stderr if a problem
is detected in LSF and the task is not run.
The exit status is -1 and an error message is printed to stderr if a system call
fails or incorrect arguments are specified.
Otherwise, the exit status is the exit status of the task.
[ Top ]
| [ Platform Documentation ] | [ Title ] | [ Contents ] | [ Previous ] | [ Next ] | [ Index ] |
|
Date Modified: February 24, 2004
Platform Computing: www.platform.com Platform Support: support@platform.com Platform Information Development: doc@platform.com Copyright © 1994-2004 Platform Computing Corporation. All rights reserved. |