Managing HP Serviceguard for Linux Ninth Edition, April 2009

It is not necessary to halt the single node in this case, since the applications are still
running, and no other node is currently available for package switching.
CAUTION: But you should not try to restart Serviceguard; data corruption might
occur if another node were to attempt to start up a new instance of an application that
is still running on the single node. Instead, choose an appropriate time to shut down
and reboot the node. This will allow the applications to shut down and Serviceguard
to restart the cluster after the reboot.
Disabling identd
Ignore this section unless you have a particular need to disable identd.
You can configure Serviceguard not to use identd.
CAUTION: This is not recommended. Consult the white paper Securing Serviceguard
at http://docs.hp.com -> High Availability -> Serviceguard ->
White Papers for more information.
If you must disable identd, do the following on each node after installing Serviceguard
but before each node rejoins the cluster (e.g. before issuing a cmrunnode or cmruncl).
For Red Hat and SUSE:
1. Change the value of the server_args parameter in the file /etc/xinetd.d/
hacl-cfg from -c to -c -i
2. Change the server_args parameter in the /etc/xinetd.d/hacl-probe file to
include the value -i
On a SUSE system, change
server_args = -f /opt/cmom/log/cmomd.log -r /opt/cmom/run
to
server_args = -i -f /opt/cmom/log/cmomd.log -r /opt/cmom/run
On A Red Hat system, change
server_args = -f /user/local/cmom/log/cmomd.log -r
/user/local/cmom/run
to
server_args = -i -f /user/local/cmom/log/cmomd.log -r
/user/local/cmom/run
3. Restart xinetd:
/etc/init.d/xinetd restart
Managing the Running Cluster 187