Controlling gWLM’s Startup Behavior

The gWLM CMS daemon (gwlmcmsd) is set to start at boot by /opt/vse/bin/vseinitconfig. Generally, you should not change this setting as it disables all VSE Management Software from starting at boot.

You can control whether the gWLM CMS daemon (gwlmcmsd) and its agent daemons on the managed nodes (gwlmagent) start at boot by:

Manually setting variables in the /etc/rc.config.d/gwlmCtl file. (The /sbin/init.d/gwlmcmsd and /sbin/init.d/gwlmagt scripts use these variables.)
Using the --enable_start_on_boot and --disable_start_on_boot options to gwlmcmsd and gwlmagent.




	NOTE: HP recommends starting these daemons at boot only when used in a secure operating environment. Setting `GWLM_CMS_START` to 0 prevents automatic use at boot of HP Integrity Essentials Virtualization Manager and HP Integrity Essentials Capacity Advisor.

The gwlmCtl file is shown below:

########################################################################
# (C) Copyright 2004-2006 Hewlett-Packard Development Company, L.P.
#
# gWLM Configuration File
#
# $Revision: 1.7 $
# $Date: 2006/05/19 17:41:10 $
########################################################################

# Set GWLM_CMS_START to 1 to have the init process start the gWLM CMS
# daemon. (HP recommends setting this variable to 1 only when used in a
# secure operating environment.)
#
# NOTE: GWLM_CMS_START=0 prevents automatic use at boot of 
#       HP Integrity Essentials Virtualization Manager and 
#       HP Integrity Essentials Capacity Advisor.
GWLM_CMS_START=0

# Set GWLM_AGENT_START to 1 to have the init process start the gWLM agent
# daemon. (HP recommends setting this variable to 1 only when used in a
# secure operating environment.)
GWLM_AGENT_START=0

# Set GWLM_HOME to the location where gWLM is installed.
# Default is /opt/gwlm.
GWLM_HOME=/opt/gwlm

Controlling gWLM’s Startup Behavior

Technical documentation

» Table of Contents