Seth Woolley's Man Viewer

state(1) - state - Report status of LAM processes - man 1 state

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

STATE(1)                         LAM COMMANDS                         STATE(1)

       state - Report status of LAM processes.

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

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

       Most  MPI  users(1,5)  will  probably not need to use the state command; see
       mpimsg(1) and mpitask(1).  This command is only  installed  if(3,n)  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(2,7) 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(1,8) order to be
       directly  visible to state.  In other cases, limited monitoring is pos-
       sible in(1,8) 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.

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

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

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

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

LAM 7.0.6                          May, 2004                          STATE(1)

References for this manual (incoming links)