HPUX ovstop[1m]

 ovstop(1M)                                                       ovstop(1M)





 NAME
      ovstop - stop HP OpenView Platforms daemon processes

 SYNOPSIS
      ovstop [-d] [-v] [object_manager_names...]

 DESCRIPTION
      ovstop stops the object managers that run as daemon processes as part
      of the HP OpenView Platforms. ovstop works by sending a stop request
      to the process management daemon, ovspmd. If called with one or more
      object_manager_name arguments, it stops the designated object
      managers. If called with no arguments, or if one of the named
      arguments is OVsPMD, it stops all object managers currently running,
      including ovspmditself.

      Unlike ovstart, ovstop will not start ovspmd if it is not already
      running.

      The object managers are configured by ovaddobj from information in
      Local Registration Files (see LRF(4)). An object manager is named by
      the first field in the LRF describing it. Unlike ovstart, ovstop
      ignores dependency information from the LRF. If other object managers
      depend on an object manager that is stopped, it is up to them to
      detect that their dependency is no longer met, and exit if
      appropriate.

      ovstop must be run by the super-user.

    Parameters
      ovstop recognizes the options described below. The first argument that
      is not an option, and any succeeding arguments, are interpreted as
      names of object managers to stop, and passed to ovspmd in the stop
      request.

      -v        By default, ovstop produces no output unless there are
                configuration or system errors.  In -v(verbose) mode, ovstop
                reports the termination of each object manager as it occurs.
                If ovspmd was started with its -V option, this status report
                will be much more extensive, including everything ovspmd
                knows about the object manager.

      -d        In -d (debug) mode, ovstop reports the important stages in
                its processing, including contacting and sending the stop
                request to ovspmd, and ovspmd closing the communication
                channel.

 DIAGNOSTICS
      ovstop reports certain command line errors (in particular, too many
      arguments) and system errors. The messages are prefixed with "
      ovstop:", and are intended to be self-explanatory.  ovstop also
      outputs error messages received ovspmd. These messages are prefixed



 Hewlett-Packard Company            - 1 -       NNM Release 4.0: August 1995






 ovstop(1M)                                                       ovstop(1M)





      with " ovspmd:". ovstop ignores unrecognized options.

 AUTHOR
      ovstop was developed by HP.

 FILES
      HP-UX 9.x and SunOS 4.1.x
                          /usr/OV/bin/ovstop
                          /usr/OV/bin/ovspmd

      HP-UX 10.x and Solaris 2.3, 2.4
                          /opt/OV/bin/ovstop
                          /opt/OV/bin/ovspmd

      Universal Pathname  $OV_BIN/ovstop
                          $OV_BIN/ovspmd


      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
      ovaddobj(1M), ovdelobj(1M), ovspmd(1M), ovstart(1M), ovstatus(1M),
      LRF(4)



















 Hewlett-Packard Company            - 2 -       NNM Release 4.0: August 1995