NIO CommKit Host Interface Installation and System Administration Manual

4-9
Administering the CommKit Software and the STREAMS Listener
Starting and Stopping the CommKit Server
# dkitrc stop
Starting and Stopping a Specific CommKit Interface Board
To start or stop the server for a specific CommKit interface board, use the -i
option with dkitrc. For example, to start the CommKit server from board 2,
enter:
# dkitrc start -i 2
To stop both the server and the listener, which are running on board 2, enter:
# dkitrc stop -i 2
Starting and Stopping the Daemon
The CommKit 4.0 software runs dkdaemon at all times, unless you explicitly
stop the daemon. To stop the daemon, check its process identification
number (PID) by entering
# ps -ef
Once you know the PID, you can enter
# kill -9 PID
to stop the process. To restart the daemon, enter
# dkdaemon -xt -i interfaceNumber
Specifying the CommKit Log Files
The log files you specify when you start the dkdaemon and dkserver
processes provide meaningful information on a running CommKit server.
The log files include information on the success or failure of the system
startup, as well as information on the handling of each incoming call.
If a problem occurs when the CommKit server is first started, you should
examine the log files. Common problems include incorrect VCS
configurations, a mismatch of the server name between the VCS and the
host, or the CPM not being in service.
When you see the following message in the CommKit server log file, you
know that the server has successfully initialized its connection with the
VCS: