Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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)

Check Out this Related Man Page

LAMHALT(1)							     LAM TOOLS								LAMHALT(1)

NAME

       lamhalt - Shutdown the LAM/MPI run-time environment.

SYNOPSIS

       lamhalt [-dhHv]

OPTIONS

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

       -h	   Print the command help menu.

       -i	   Return immediately (even before the LAM universe is fully halted); deprecated

       -H	   Suppress printing the header message.

       -v	   Be verbose.

DESCRIPTION

       The  lamhalt  tool  terminates the LAM software on each of the nodes that were initially booted with lamboot and/or lamgrow.  No additional
       command line arguments are necessary - lamhalt simply sends a message to each remote node telling  it  to  shut	down.	Each  remote  node
       invokes tkill(1) locally to shut down.  See tkill(1) for a description of how LAM is terminated on each node.

       lamhalt	may  fail  if one of the remote nodes has failed, and does not respond to lamhalt's queries.  In this case, the lamwipe(1) command
       should be used to shut down LAM/MPI.  If lamwipe(1) fails, the user can manually invoke tkill(1) on the troubled node.  In  extreme  cases,
       the user may have to terminate individual LAM processes with kill(1).

       Older  versions of lamhalt would return 1-3 seconds before the entire LAM universe was shut down.  This caused problems for some LAM users,
       particularly those who had scripts that invoked lamboot immediately after lamhalt.  lamhalt has therefore been changed to  wait	until  the
       entire LAM universe is down before exiting.  This makes the execution of lamhalt take a few seconds (typically less than 5).

       For  users  who	want  the old lamhalt behavior, use the -i (or "immediate") switch, which will cause lamhalt to return immediately, likely
       before the entire LAM universe has been taken down.

EXAMPLES

       lamhalt -d
	   Shutdown LAM on the machines and be verbose about its actions.

SEE ALSO

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

LAM 7.1.4							    July, 2007								LAMHALT(1)
Man Page