3.1.2 Matrix Server Administration Guide

Chapter 2: Matrix Administration 32

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.

NOTE: When you invoke mxinit to start Matrix Server, by default it

continues running and monitors processes. If you do not want

mxinit to monitor processes, invoke it with the -M (or

--no-monitor) option. It will then exit after it completes the

options you specified.

View Matrix Server Process Status

You can use the mxinit utility or the pmxs script to display the status of

Matrix Server processes and modules. To display status information with

mxinit, either invoke it with no options or specify the --status option. You

can also use the command /etc/init.d/pmxs status to display this

information. You do not need to be user root.

$ /opt/polyserve/bin/mxinit --status

Matrix Server Status:

Name pid / status

mxinit 15930 mxinit: Monitoring MxS processes

mxlog Loaded

grpcommd 15885

mxlogd 15887

pswebsvr 15890

clusterpulse 15892

panpulse 15912

psd_devfs Loaded

mxinit The mxinit daemon

pswebsvr The embedded web server daemon used by the

Management Console and the mx utility