When I tried to upgrade to LAM 7.0.4 some scripts that have been using
6.6b2, it took me a while to figure out what was wrong with 'lamboot
-xsHb'. Having correct help from lamboot would have given me the answer
instantly. The -s option is missing from the help message's synopsis,
so I guessed that it had not made it into this version of lamboot. And
the form of the synopsis implied that it would accept multiple
single-character options, which it does not. 'lamboot -x -s -H -b'
works fine.
Evidence:
~ 63% lamboot -h
-----------------------------------------------------------------------------
Synopsis: lamboot [-bdhHlvVx] [-nn] [-np] [-c <conf file>] [<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
-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 directory:
...
~ 64% lamboot -V
LAM 7.0.4/MPI 2 C++/ROMIO - Indiana University
Arch: x86_64-unknown-linux-gnu
Prefix: /netDISKS/master/netmt/LINUX_AMD64/lam-7.0.4
Configured by: hadsell
Configured on: Tue Mar 16 17:50:59 EST 2004
Configure host: ibmloana
SSI rpi: crtcp lamd sysv tcp usysv
--
Dick Hadsell 914-259-6320 Fax: 914-259-6499
Reply-to: hadsell_at_[hidden]
Blue Sky Studios http://www.blueskystudios.com
44 South Broadway, White Plains, NY 10601
|
