The following is a brief description of how tasks are qualified for LSF processing.
Commands are chosen to run on the least heavily loaded eligible workstation, depending upon upon the qualified task list. There are two lists of tasks which define the commands that are eligible for remote execution and those requiring local execution.
The lsrtasks command displays the list of commands that may be submitted to any eligable, lightly-loaded workstation in the cluster.
marple:-~ >lsrtasks CC fgrep pic ar g++/cpu psroff as gcc/cpu sort c89/cpu gprof spell cc/cpu grap/- split compress/-:cpu:mem grep/- tbl compressdir/cpu:mem gtar tpc deroff gzip troff/cpu diff ispell ttc ditroff latex/cpu uncompress/cpu:mem du lint uuencode/cpu dvi2ps ls wc egrep make/cpu what eqn ncftp zcat/cpu:mem f77/cpu nroff/cpu zmore/cpu f90 od marple:-~ >
Some commands relate specifically to conditions on the local machine, and they should be executed on the local machine. The lsltasks command will list all the commands that should be executed locally.
marple:-~ >lsltasks at du mount pwd sa tty vmstat crontab finger netstat renice showmount uname who df mail ps rlogin top uptime marple:-~ >
Commands may be added to or removed from each of the lists by following the lsltasks or lsrtasks command with a + or - followed by the name of the command to be added or removed.
For example, to force execution of the Fortran90 compiler on a remote machine:
marple:-~ >lsrtasks +f90 marple:-~ >Commands can be removed similarly:
marple:-~ >lsltasks -du marple:-~ >
The LSF command lists may be personalized automatically by entering the changes in $HOME/.lsftask. See lsf.task for more information.