3.5.1 Matrix Server Command Reference

Chapter 1: Matrix Server Commands 15

-p <password>

Specify the password needed to access the remote controller.

mxinit – manage Matrix Server processes

Synopsis

/opt/polyserve/bin/mxinit [-s, --start]

[-x, --stop]

[-H, --hard]

[-g, --status]

[-L, --load-mod]

[-U, --unload-mod]

[-f file, --alt-config-file file]

[-m, --monitor]

[-M, --no-monitor]

[--hba-status]

[--status]

[--version]

[-v, --verbose]

[-h, -?, --help]

Description

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.

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.

Typically, you should use the pmxs script to start or stop Matrix Server.

However, if you want to see verbose output during the start or stop operation,

you can run mxinit manually with the --verbose option.

mxinit performs its actions according to a set of default values. You can use

the /etc/opt/polyserve/mxinit.conf configuration file to override the default