Assume local and remote shell are the same. This means that only one
remote shell invocation is used to each node. If
is not used, two remote shell invocations are used to each node.
Turn on debugging mode. This implies -v.
Print the command help menu.
Lamwipe only the first <#> nodes.
Use the LAM installation specified in
-ssi <key> <value>
Send arguments to various SSI modules. See the "SSI" section, below.
Don't add "-n" to the remote agent command line
Do not force the execution of $HOME/.profile on remote hosts
Set the session prefix, overriding LAM_MPI_SESSION_PREFIX.
Set the session suffix, overriding LAM_MPI_SESSION_SUFFIX.
Override the internal installation path. For internal use only, do
not use unless you know what you are doing.
This command has been deprecated in favor of the
should only be necessary if
fails and is unable to clean up the LAM run-time environment properly.
tool terminates the LAM software on each of the machines specified in the
is the topology tool that terminates LAM on the UNIX(tm) nodes of a
It invokes tkill(1) on each machine.
See tkill(1) for a description of how LAM is terminated on
file is a LAM boot schema written in the host file syntax. CPU counts
in the boot schema are ignored by
See bhost(5). Instead of the command line, a boot schema can be
specified in the LAMBHOST environment variable. Otherwise a default
file, bhost.def, is used. LAM searches for
first in the local directory and then in the installation directory
does not quit if a particular remote node cannot be reached
or if tkill(1) fails on any node.
A message is printed if either of these failures occur, in which
case the user should investigate the cause of failure and,
if necessary, terminate LAM by manually executing tkill(1)
on the problem node(s).
In extreme cases, the user may have to terminate individual
LAM processes with kill(1).
will terminate after a limited number of nodes if the
option is given.
This is mainly intended for use by lamboot(1), which invokes
when a boot does not successfully complete.
SSI (System Services Interface)
switch allows the passing of parameters to various SSI modules. LAM's
SSI modules are described in detail in lamssi(7). SSI modules have
direct impact on MPI programs because they allow tunable parameters to
be set at run time (such as which boot device driver to use, what
parameters to pass to that driver, etc.).
switch takes two arguments:
argument generally specifies which SSI module will receive the value.
For example, the
"boot" is used to select which RPI to be used for starting processes
on remote nodes. The
argument is the value that is passed. For example:
lamboot -ssi boot tm
Tells LAM to use the "tm" boot module for native launching in PBSPro /
OpenPBS environments (the tm boot module does not require a boot
Tells LAM to use the "rsh" boot module, and tells the rsh module to
use "ssh -x" as the specific agent to launch executables on remote
And so on. LAM's boot SSI modules are described in lamssi_boot(7).
switch can be used multiple times to specify different
arguments. If the same
is specified more than once, the
are concatenated with a comma (",") separating them.
Note that the
switch is simply a shortcut for setting environment variables. The
same effect may be accomplished by setting corresponding environment
variables before running
The form of the environment variables that LAM sets are:
Note that the
switch overrides any previously set environment variables. Also note
arguments are still set as environment variable -- they are not
for correctness. Illegal or incorrect
arguments may or may not be reported -- it depends on the specific SSI
Remote Executable Invocation
All tweakable aspects of launching executables on remote nodes during
are discussed in lamssi(7) and lamssi_boot(7). Topics include (but
are not limited to): discovery of remote shell, run-time overrides of
the agent use to launch remote executables (e.g., rsh and ssh), etc.
lamwipe -v mynodes
Shutdown LAM on the machines described in the boot schema,
Report about important steps as they are done.
default boot schema file, where "laminstalldir" is the directory where
LAM/MPI was installed.