Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add cpuS and wVip to status list - CommandLineGuide.rst #1263

Merged
merged 1 commit into from
Oct 17, 2024
Merged

Add cpuS and wVip to status list - CommandLineGuide.rst #1263

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/source/Explanation/CommandLineGuide.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -542,6 +542,7 @@ The second row of output gives detailed headings within each category:
The configurations are listed on the left. For each configuraion, the state
will be:

* cpuS: process is expensive in CPU usage (runStateThreshold_cpuSlow)
* disa: disabled, configured not to run.
* hung: processes appear hung, not writing anything to logs.
* idle: all processes running, but no data or message transfers for too long (runStateThreshold_idle)
Expand All @@ -552,6 +553,7 @@ will be:
* run: all processes are running (and transferring, and not behind, and not slow... normal state.)
* slow: transfering less than minimum bytes/second ( runStateThreshold_slow )
* stop: no processes are running.
* wVip: process doesn't have the vip (only applies when the vip option is specified in the config)

The next columns to the right give more information, detailing how many processes are Running, out of the number expected.
For example, 3/3 means 3 processes or instances found of the 3 expected to be found.
Expand Down
Loading