wipe(1) [redhat man page]

WIPE(1) 							     LAM TOOLS								   WIPE(1)

NAME

       wipe - Shutdown LAM.

SYNTAX

       wipe [-bdhv] [-n <#>] [<bhost>]

OPTIONS

       -b	   Assume  local  and remote shell are the same.  This means that only one remote shell invocation is used to each node.  If -b is
		   not used, two remote shell invocations are used to each node.

       -d	   Turn on debugging mode.  This implies -v.

       -h	   Print the command help menu.

       -v	   Be verbose.

       -n <#>	   Wipe only the first <#> nodes.

DESCRIPTION

       This command has been deprecated in favor of the lamhalt command.  wipe should only be necessary if lamhalt fails and is unable to clean up
       the  LAM  run-time  environment	properly.  The wipe tool terminates the LAM software on each of the machines specified in the boot schema,
       <bhost>.  wipe is the topology tool that terminates LAM on the UNIX(tm) nodes of a multicomputer  system.   It  invokes	tkill(1)  on  each
       machine.  See tkill(1) for a description of how LAM is terminated on each node.

       The  <bhost>  file is a LAM boot schema written in the host file syntax.  CPU counts in the boot schema are ignored by wipe.  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 <bhost> first in the local directory and then in the installation directory under etc/.

       wipe 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).

       wipe  will  terminate  after  a	limited  number  of nodes if the -n option is given.  This is mainly intended for use by lamboot(1), which
       invokes wipe when a boot does not successfully complete.

EXAMPLES

       wipe -v mynodes
	   Shutdown LAM on the machines described in the boot schema, mynodes.	Report about important steps as they are done.

FILES

       $LAMHOME/etc/lam-bhost.def	 default boot schema file

SEE ALSO

       recon(1), lamboot(1), tkill(1), bhost(5), lam-helpfile(5)

LAM 6.5.8							  November, 2002							   WIPE(1)

LAMGROW(1)							   LAM COMMANDS 							LAMGROW(1)

NAME

       lamgrow - Extend a LAM multicomputer.

SYNTAX

       lamgrow [-hv] [-c <bhost>] [-u <userid>] [<node>] <hostname>

OPTIONS

       -h	     Print useful information on this command.

       -c <bhost>    Update this boot schema.

       -v	     Be verbose.

       <hostname>    Extend LAM with this host.

       <node>	     Assign this ID to the new node.

       -u <userid>   Use this userid to access the new host.

DESCRIPTION

       An existing LAM session, initiated by lamboot(1), can be enlarged to include more nodes with lamgrow.  One new node is added for each invo-
       cation.	At a minimum, the host name that will run the new node is given on the command line.  If a different userid is required to  access
       the host, it is specified with the -u option.

       It  can be useful to update the original boot schema used by lamboot(1) with the new node added by lamgrow.  The -c option specifies a boot
       schema filename and causes lamgrow to append the host name.  The updated boot schema is ready to be used by wipe(1) to  terminate  the  ex-
       tended  LAM session.  New nodes added by lamgrow will not be cleaned up by wipe(1) if the original boot schema is used.	They can be termi-
       nated individually, as always, with tkill(1).

       The new node can be assigned any unused, non-negative identifier.  If no identifier is specified, the highest node identifier in  the  cur-
       rent LAM session plus one is used.  Note that lamboot(1) always assigns node identifiers consecutively from 0.

       lamgrow	can be run from any node.  As a LAM command program it must be run from a node in the existing LAM session.  It cannot be run from
       the intended new host.  Two invocations of lamgrow should not run concurrently and the command attempts to detect this situation.  There is
       no  protection  against specifying the name of host that is already part of the user's existing LAM session.  This is not the proper use of
       lamgrow.

       Resource managers will be the most common user of lamgrow.  When hosts become idle and a user has expressed a desire to	the  manager  that
       extra cycles should be exploited, the manager could invoke lamgrow and then launch the specified application process(es) on the new node.

EXAMPLES

       lamgrow -v newhost
	   Start  LAM  on  newhost  and  add it to the existing LAM session.  Choose the next available node identifier and report about important
	   steps as they are done.

       lamgrow n30 newhost
	   Start LAM on newhost with node ID 30 and add it to the existing LAM session.  Operate silently.

FILES

       $LAMHOME/etc/lam-conf.lam	 default configuration file for LAM nodes

SEE ALSO

       lamboot(1), hboot(1), wipe(1), tkill(1), bhost(5), conf(5)

LAM 6.5.8							  November, 2002							LAMGROW(1)