lamboot -V (return code: 0)
LAM 7.1.4/MPI 2 C++/ROMIO - Indiana University
Arch: x86_64-pc-linux-gnu
Prefix: /usr/lib/lam
Configured by: buildd
Configured on: Thu Apr 10 03:20:43 UTC 2014
Configure host: phianna
SSI rpi: crtcp lamd sysv tcp usysv
lamboot -HELP (return code: 226)
-----------------------------------------------------------------------------
Synopsis: lamboot [-b] [-d] [-h] [-H] [-l] [-s] [-v] [-V] [-x] [-nn] [-np]
[-c <conf file>] [-prefix </lam/install/path/>]
[-ssi <key> <value>] [<bhost>]
Description: Start up a LAM universe
Options:
-b Use the faster boot algorithm; will only work if shell
on all remote nodes is same as shell on local node
-c Use <conf file> for start-up configuration.
Unless you are a developer, you probably don't want
to use this option.
-d Print debugging messages (implies -v)
-h Print this message
-H Don't print the header
-l Use local hostnname resolution (vs. centralized name lookup)
-nn Don't add "-n" to the remote agent command line
-np Do not force the execution of $HOME/.profile on remote
hosts
-prefix Use the LAM installation specified in </lam/install/path>
-ssi Send arguments to various SSI modules. See the
lamboot manpage for SSI options.
-s Close stdout/stderr of the locally-launched LAM daemon
-v Be verbose
-V Print version and exit without booting
-x Run nodes in fault tolerant mode
<bhost> Use <bhost> as the boot schema
-session-prefix
Set the session prefix, overriding LAM_MPI_SESSION_PREFIX.
-session-suffix
Set the session suffix, overriding LAM_MPI_SESSION_SUFFIX.
-withlamprefixpath
Override the internal installation path. For internal
use only, do not use unless you know what you are doing.
Session directory:
A LAM session directory will be created on each node where the
LAM run-time environment is started. This directory must be
unique to each node. It will be created in the form:
<prefix>/lam-<username>@<hostname>[-<suffix>]
<prefix> will be based on the following search order:
1. The value of the LAM_MPI_SESSION_PREFIX environment
variable (if it exists).
2. The value of the TMPDIR environment variable (if it
exists).
3. /tmp
<suffix> will be based on the following search order (if a
valid <suffix> is not found, it is not used):
1. The value of the LAM_MPI_SESSION_PREFIX environment
variable (if it exists).
2. If running under a supported batch system, a unique job ID
will be used.
The suffix is specifically for the case where users need
multiple LAM run-time environments on a single node (as is
common in batch-queue environments).
-----------------------------------------------------------------------------