HPUX ovspmd[1m]
ovspmd(1M) ovspmd(1M)
NAME
ovspmd - HP OpenView Platforms process management daemon
SYNOPSIS
ovspmd [-V] [-f startup_file]
DESCRIPTION
ovspmd manages the daemon processes that are part of the HP OpenView
Platforms, starting, stopping, and reporting status on them in
response to requests from the user interface programs ovstart, ovstop,
and ovstatus. ovspmd is normally started automatically by ovstart.
ovstart requests ovspmd to start the object manager programs specified
in the HP OpenView Platforms startup file (SUF), by default ovsuf.
Object managers (Ms) are configured in a local registration file (LRF)
and added to the SUF by ovaddobj. If ovstart is called with no
arguments, ovspmd will start all Ms configured to run by default (that
is, with initial start flag OVs_YES_START in the LRF).
ovstop requests ovspmd to stop configured Ms. If ovstop is called with
no arguments, ovspmd will stop all currently running
ovstatus requests ovspmd to report the current running status of
configured Ms.
Ms are started by ovspmd as daemons, that is, in the background, with
' /' as their working directory, and with stdin, stdout, and stderr
attached to /dev/null.
Each M can be configured with a "dependency list," that is, a list of
other Ms that must already be running before this M can be started
successfully. ovspmd will not start an M until all the Ms on which it
depends have already initialized successfully.
ovspmd distinguishes among three classes of object managers:
OVs_WELL_BEHAVED
A well-behaved M uses the OVsPMD API (see OVsPMD_API(3)) to
communicate with ovspmd. It sends ovspmd status information
regarding successful and ovspmd considers a well-behaved M
to have initialized successfully only when it explicitly
reports that it has. A well-behaved M also exits when it
receives the command OVS_CMD_EXIT from ovspmd.
The status information passed by the M to ovspmd is
forwarded to ovstart or ovstop, if currently running. The
last message received from each M is saved, and forwarded,
on request, to ovstatus. The messages received from well-
behaved nettl logging and tracing facility, in the OVS
subsystem. Messages indicating normal events, such as
successful initialization, are logged at the INFORMATIVE
Hewlett-Packard Company - 1 - NNM Release 4.0: August 1995
ovspmd(1M) ovspmd(1M)
level. Messages indicating initialization failure or
abnormal termination are logged at the WARNING level.
OVs_NON_WELL_BEHAVED
ovspmd can also manage object managers that do not use the
OVsPMD API (non-well-behaved Ms) only if ovspmd considers
such an M to have initialized successfully if it has not
exited after the timeout configured for it in its LRF.
Non-well-behaved Ms are terminated with SIGTERM rather than
with a command. They are sent SIGKILL if they do not exit
within the configured timeout.
OVs_DAEMON
Ms that go into the background cannot be managed either with
a communication channel or with signals. ovspmd can start
such an M, but cannot stop or report meaningful status about
it, since it has neither a communication channel nor a
process ID for it.
Parameters
-V Run in verbose mode. In this mode, ovspmd outputs very
detailed information about the configuration of Ms. This is
far too much information for ordinary use.
-f startup_file
Read startup_file as the startup file (SUF) instead of the
default. Note that startup_file must be an absolute path.
DIAGNOSTICS
ovspmd issues error messages regarding configuration errors and system
call failures. These messages are intended to be self-explanatory. If
it currently has an open communication channel with one of the user
interface programs ovstart, ovstop, or ovstatus, ovspmd outputs error
messages through the
In addition, ovspmd logs configuration and system errors using nettl
in the OVS subsystem at the ERROR level.
AUTHOR
ovspmd was developed by HP.
FILES
HP-UX 9.x and SunOS 4.1.x
/usr/OV/bin/ovspmd
/usr/OV/conf/ovsuf
/usr/OV/conf/LANG
HP-UX 10.x and Solaris 2.3, 2.4
/opt/OV/bin/ovspmd
Hewlett-Packard Company - 2 - NNM Release 4.0: August 1995
ovspmd(1M) ovspmd(1M)
/etc/opt/OV/share/conf/ovsuf
/etc/opt/OV/share/conf/LANG
Universal Pathname $OV_BIN/ovspmd
$OV_DB/snmpCollect/ovsuf
$OV_CONF/LANG
Universal pathname paths are established according to your shell and
platform requirements. See the file that applies to your platform and
shell for more information about the script used to set HP OpenView
Network Node Manager environment variables:
HP-UX 9.x and SunOS 4.1.x
/usr/OV/bin/ov.envvars.sh (k shell)
/usr/OV/bin/ov.envvars.csh (c shell)
HP-UX 10.x and Solaris 2.3, 2.4
/opt/OV/bin/ov.envvars.sh (k shell)
/opt/OV/bin/ov.envvars.csh (c shell)
SEE ALSO
nettl(1M), ovaddobj(1M), ovdelobj(1M), ovstart(1M), ovstatus(1M),
ovstop(1M), kill(2), OVsPMD_API(3), LRF(4), lang(5), signal(5).
EXTERNAL INFLUENCES
Environment Variables
ovspmd sets the environmental variable LANG for itself and the daemon
processes it starts by reading the file LANG which, if present, should
contain only the single-word value to which LANG should be set. LANG
determines the language in which messages appear. If LANG does not
exist, and if LANG is not set or is set to the empty string, a default
of "C" (see lang(5)) is used.
Hewlett-Packard Company - 3 - NNM Release 4.0: August 1995