![](/images/backgrounds/285892/hp-xc-system-2-x-software-users-manual-156197106x1.png)
Example 7-20: View Job Details in LSF (cont.)
<normal>, 4 Processors Requested;
date and time stamp: Dispatched to 4 Hosts/Processors <4*lsfhost.localdomain>
;
date and time stamp:
date and time stamp: Starting (Pid 13938);
Summary of time in seconds spent in various states by | date | and time stamp | |||||
PEND | PSUSP | RUN | USUSP | SSUSP | UNKWN | TOTAL | |
9 | 0 | 251 | 0 | 0 | 0 | 260 |
|
|
|
|
|
|
|
|
|
Example 7-21: Running Jobs from an xterm Window
$ hostname
n1
$ srun hostname
n1
n2
n3
n4
$ srun
n1 n2
When you finish with your interactive session, exit from the terminal window. This completes your job in
7.6.2 Submitting an Interactive Job to Launch a Shell
You can submit an interactive shell, such as the Korn shell or bash, as the jobname parameter when you submit a job to
Example 7-22: Submitting an Interactive Shell Program
$ bsub
<<Starting on lsfhost.localdomain>> hostname
n1
srun hostname n1
n1
n2
n2
exit
$
The obvious limitation is the absence of the shell prompt. Signal support is also limited.
The job starter script uses the srun command to execute a job on the first allocated node instead of the LSF execution host. The srun command does not provide full tty support; it simply executes the program it was given and sets up I/O connections for STDIN, STDOUT, and STDERR of the program back to the launching process.
If this type of interaction is needed often, ask the system administrator to configure a special queue in