Rechercher une page de manuel

Chercher une autre page de manuel:

state

Langue: en

Autres versions - même langue

Version: 179487 (CentOS - 06/07/09)

Section: 1 (Commandes utilisateur)

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 status 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 execution 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 function that caused the current execution state. In general, the information provided by state is low-level and geared toward LAM system programmers. 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 possible 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 giving 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)
Toi, qui me lis, es-tu sûr de comprendre ma langue ?
-+- Jorge Luis Borges (1899-1986), La bibliothèque de Babel -+-