3.5.1 Matrix Server Administration Guide

Chapter 2: Matrix Administration 36
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
Matrix Server Processes and mxinit
When Matrix Server is running on a server, the following Matrix Server
processes should be active:
Do not terminate any of these processes; they are required for Matrix
Server operations.
Process Monitoring
The mxinit utility is started automatically as a daemon on each server
and monitors all Matrix Server processes running there. (You can start
another instance of mxinit to perform other tasks provided by the utility.)
If a Matrix Server process dies unexpectedly on a server, mxinit will
restart it if possible. However, certain process failures may force a restart
of that particular server.
clusterpulse The ClusterPulse daemon
panpulse The PanPulse daemon
sanpulse The SANPulse daemon
dlm The Distributed Lock Manager daemon
grpcommd The matrix-wide communications daemon
mxregd The daemon that manages portions of the internal Matrix
Server configuration
mxeventd The distributed event subscription and notification
service
mxlogd The log daemon
mxperfd The daemon responsible for gathering performance data
mxinit The mxinit daemon
pswebsvr The embedded web server daemon used by the
Management Console and the mx utility