NIO CommKit Host Interface Installation and System Administration Manual

DKDAEMON(1M) DKDAEMON(1M)
E-21 CommKit Host Interface, Release 4.0
NAME
dkdaemon – host interface daemon process
SYNOPSIS
dkdaemon [ –i interface ] [ –t ] [ –x ] [ –l logfile] [ -v verbosity ] [ –a [acctfile] ] [ –c channels ]
[ –b urpblocks ] [ –p protocol ] [ -w windowsize ]
DESCRIPTION
dkdaemon is the host interface daemon process. The primary purposes of dkdaemon are to: 1) retain the
dkux(7) call processing module on each dkhs(7) Stream associated with an AT&T data switch Common
Signaling Channel, 2) support accounting, logging and auditing, and, 3) provide dynamic linking and
unlinking of dkhs(7) Streams for the remote execution [See dkxqt(7)] and TLI [See dktli(7)] subsystems. All
actions of dkdaemon are controlled via command line arguments.
The following arguments select the subsystem or subsystems that will be serviced and may be specified in
any combination and order:
–i interface Service dkhs(7) physical interface number interface. One –i option may be specified for
each installed interface board.
–t Service the dktm TLI subsystem driver.
–x Service the dkxqt(7) remote execution subsystem driver.
When invoked with none of the above options, dkdaemon services all possible dkhs(7) interfaces and
subsystems. When any of these options are used it limits dkdaemon to servicing the specified subsystem(s)
or interface(s). If multiple dkdaemon processes are used with overlapping services, only one dkdaemon will
support the service. Using the default action may result in the logging of extraneous ERROR or WARNING
messages in a less than fully configured system.
Several command line arguments may be used to alter the default logging and auditing modes of dkdaemon:
–l logfile Use logfile for activity logging instead of the default file /var/opt/dk/log/dkdaemonlog. The
full pathname for logfile must be specified or the logfile will be created in /var/opt/dk/log.
This audit trail includes: a) activity/status, ERROR and WARNING messages that are
described in the DIAGNOSTICS section, b) connection auditing messages described in
dkaudit(4), and c) undocumented debugging messages that appear only at high verbosity
levels.
–v verbosity Use verbosity as the logging level instead of the default value of 5. The normal range for
log level is 1 through 9. A larger verbosity number means more log detail is desired.
Increasing the logging verbosity above nine will cause the logging file to grow large with
undocumented and useless messages very quickly. The verbosity level must be between 1
and 99 (inclusive).
–a [acctfile] Enable dkhs(7) data transfer, connect time accounting, and optionally use acctfile as the
accounting file instead of the default file /var/opt/dk/log/dkacct. The full pathname for
acctfile must be specified or the acctfile will be created in /var/opt/dk/log. The format of
these accounting records is described in dkacct(4).
When dkdaemon contacts the dkux(7) module for each physical dkhs(7) interface, it configures several
global interface parameters with built-in default values that may be overridden through command line
options. These options and the built-in default values are described below. The built-in default values are
adequate for all customer installations and these options are provided for advanced host applications and for
developer convenience. The parameters apply to all dkhs(7) interfaces controlled by the dkdaemon process.
Use a separate dkdaemon process for each interface if you wish to vary the parameters for each interface.