NIO CommKit Host Interface Installation and System Administration Manual

4-8
Administering the CommKit Software and the STREAMS Listener
Starting and Stopping the CommKit Server
Starting and Stopping the CommKit Server
To start the CommKit server, log on as superuser and then enter a dkserver
command in the following form:
# dkserver -i interfaceNumber -s server -l logFile
The -i option specifies the CommKit interface board to start (numbered from
0 to 7), the -s option specifies the server name, and the -l option specifies the
log file in which system messages will be stored.
To stop the server, enter a dkserver command with the -t option:
# dkserver -t -i interfaceNumber -s server
The dkserver -t command stops the server gracefully, so that the server
refuses any new calls and continues processing any ongoing calls.
You would usually start the server at boot time and terminate it just prior to
shutting down the system or switching to single-user mode.
If the CommKit server has more than one CommKit interface board
installed, you must use both the -s server and -i interfaceNumber options to
specify the server you want to terminate. For example, the following
command terminates the server named newjersey:
# dkserver -t -i 1 -s newjersey
For more information on the dkserver command, refer to the dkserver(1M)
manual page.
Starting and Stopping All Servers
To simplify starting and stopping the CommKit servers,the CommKit 4.0
software provides a script named dkitrc. The dkitrc script starts the
CommKit daemon (dkdaemon) using the information in the /etc/rc.config.d/
dkit file. To customize the defaults for your network, edit the /etc/rc.config.d/
dkit file. Refer to the dkserver(1M) man page in this manual for more details.
To start all the Datakit servers, enter
# dkitrc start
To stop all the servers and listeners, enter