ovstatus — report status of NNM managed processes
ovstatus reports the current status of the NNM managed
processes. ovstatus sends a status
request (OVS_REQ_STATUS) to the
process management process (UNIX operating system) or service
(Windows operating system), ovspmd. If called with one or more managed_process_name arguments, it reports the status for the designated managed
processes. If called with no arguments, it reports the status of
all managed processes that have been added to the NNM startup file (SUF),
including ovspmd itself.
Unlike ovstart, ovstatus does not start ovspmd if it is not already running.
The managed processes are configured by ovaddobj from information in Local Registration Files (see lrf(4)). A
managed process is named by the first field in the LRF describing
it.
ovstatus recognizes the option described below. The first
argument that is not an option, and any succeeding arguments, are
interpreted as names of managed processes for which to report status,
and are passed to ovspmd in the status request.
-c
Output one status line for each managed process.
-d
Report the important stages in its processing, including
contacting and sending the status request to ovspmd, and closing the communication channel.
-v
Print verbose messages from managed processes. In
particular, this option displays the verbose message from ovuispmd describing all current ovw sessions.
ovstatus normally exits with the status 0 (zero). It returns a non-zero status only if there
is a system problem, such as ovspmd not running.
ovstatus reports certain command-line errors (in particular,
too many arguments) and system errors. The messages are prefixed
with
ovstatus:, and are intended to be self-explanatory. ovstatus also outputs error messages received from ovspmd. These messages are prefixed with ovspmd:. ovstatus ignores unrecognized options.
ovstatus reports the known
state of all OVs_WELL_BEHAVED
and OVs_NON_WELL_BEHAVED
processes. OVs_DAEMON processes
run outside of ovspmd
control. They report a PID, a state of
unknown, and a final message of
Does not communicate with
ovspmd , as
ovspmd cannot track these
processes.
Note that ovspmd can
process multiple requests
(ovstart,
ovstop, or
ovstatus) at a time. If any of
these commands is being handled, the new request will be queued
by type until the previous command has completed.
The environment variables below represent universal
pathnames that are established according to your shell and
platform requirements. See the nnm.envvars reference page (or the UNIX manpage) for information about using environment
variables for the following files:
Windows: %NNM_BIN%\ovstatus
Windows: %NNM_BIN%\ovspmd
UNIX: $NNM_BIN/ovstatus
UNIX: $NNM_BIN/ovspmd
$LANG provides a default value if the internationalization
variables, LC_ALL, LC_CTYPE, and LC_MESSAGES are unset, null, or invalid.
If $LANG is unset, null, or invalid, the default value
of C (or English_UnitedStates.1252 on Windows) is used.
LC_ALL (or $LANG) determines the locale of all other processes
started by ovspmd .
LC_CTYPE determines the
interpretation of text as single and/or multi-byte characters,
the classification of characters as printable, and the
characters matched by character class expressions in regular
expressions.
LC_MESSAGES determines
the language in which messages are displayed.