state man page on YellowDog

Man page or keyword search:  
man Server   18644 pages
apropos Keyword Search (all sections)
Output format
YellowDog logo
[printable version]

STATE(1)			 LAM COMMANDS			      STATE(1)

NAME
       state - Report status of LAM processes.

SYNTAX
       state [-ghklt] <nodes> [<processes>]

OPTIONS
       -g      Print information on system and application processes.

       -h      Print the command help menu.

       -k      Only obtain kernel information on local kernel processes.

       -l      Print supplementary information.

       -t      Print information on system processes only.

DESCRIPTION
       Most  MPI  users	 will  probably not need to use the state command; see
       mpimsg(1) and mpitask(1).  This command is only	installed  if  LAM/MPI
       was configured with the --with-trillium switch.

       If  no process selection is given on the command line, one line of sta‐
       tus will be printed for every process on each specified node.

       In default mode, information is organized under the following headings:

       NODE	 the nodeid on which the process is running

       INDEX	 the LAM process index

       PID	 the process identifier from the underlying operating system

       KPRI	 the LAM kernel priority

       KSTATE	 the LAM kernel execution status:

		 R	   running - unencumbered by LAM

		 BR	   blocked receiving - The blocked message  event  and
			   type are also displayed.

		 BS	   blocked  sending  -	The  blocked message event and
			   type are also displayed.

		 F	   no longer a LAM process

       PROGRAM	 the program filename

       With the -l option, state prints signal information instead  of	execu‐
       tion status.

       SIGS	 all pending but undelivered LAM signals

       Some  event/type	 combinations  are  used  by  the  system to implement
       client/server requests or to implement other message passing libraries.
       Where possible, state replaces these numbers with the name of the func‐
       tion that caused the current execution state.  In general, the informa‐
       tion  provided  by state is low-level and geared toward LAM system pro‐
       grammers.  MPI programmers are expected to use  mpitask(1)  to  monitor
       the state of MPI processes.

   Kernel Processes
       A process must call kenter(2) or be created by loadgo(1) in order to be
       directly visible to state.  In other cases, limited monitoring is  pos‐
       sible in one of two ways.  If a process identifier is given, the kernel
       on each	specified  node	 will  be  consulted  for  kernel  information
       (kstate(2)).  On the local node (use node specifier h) a process can be
       watched without the assistance of the process management daemon by giv‐
       ing the process identifier and the -k option.

EXAMPLES
       state n0-7
	   Display  the status of all application processes on nodes 0 through
	   7.

       state n7 i4
	   Display the status of LAM process index 4 on node 7.

DIAGNOSTICS
       If no processes are found, only the title line is displayed.

SEE ALSO
       loadgo(1), mpimsg(1), mpitask(1), doom(1), bfstate(1)

LAM 7.1.2			  March, 2006			      STATE(1)
[top]

List of man pages available for YellowDog

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net