Managing Serviceguard 14th Edition, June 2007

Understanding Serviceguard Software Components
Serviceguard Architecture
Chapter 356
hacl-cfg dgram udp wait root /usr/lbin/cmclconfd cmclconfd -p
hacl-cfg stream tcp nowait root /usr/lbin/cmclconfd cmclconfd -c
Then force inetd to re-read inetd.conf:
/usr/sbin/inetd -c
You can check that this did in fact disable Serviceguard by trying the
following command:
cmquerycl -n nodename
where nodename is the name of the local system. If the command fails,
you have successfully disabled Serviceguard.
NOTE You should not disable Serviceguard on a system on which it is actually
running. If you are not sure, you can get an indication by means of the
command:
ps -e | grep cmclconfd
If there are cmclconfd processes running, it does not mean for certain
that Serviceguard is running on this system (cmclconfd could simply be
handling UDP queries from a Serviceguard cluster on the same subnet)
but it does mean you should investigate further before disabling
Serviceguard.
Cluster Daemon: cmcld
This daemon determines cluster membership by sending heartbeat
messages to cmcld daemons on other nodes in the Serviceguard cluster.
It runs at a real time priority and is locked in memory. The cmcld
daemon sets a safety timer in the kernel which is used to detect kernel
hangs. If this timer is not reset periodically by cmcld, the kernel will
cause a system TOC (Transfer of Control) or INIT, which is an
immediate system reset without a graceful shutdown. (This manual
normally refers to this event simply as a system reset.) This could occur
because cmcld could not communicate with the majority of the cluster’s
members, or because cmcld exited unexpectedly, aborted, or was unable
to run for a significant amount of time and was unable to update the
kernel timer, indicating a kernel hang. Before a system reset resulting