NIO CommKit Host Interface Installation and System Administration Manual

DKSERVER(1M) DKSERVER(1M)
E-32 CommKit Host Interface, Release 4.0
NAME
dkserver – handle incoming calls from an AT&T data switch network
SYNOPSIS
dkserver [ –i interface ] [ –s servername ] [ –v verbosity ] [ –c controltab ] [ -u uidfile ] [ –e ] [ –S ]
[ –l logfile ][–C channel ] [ –r ]
dkserver -t [ –i interface ] [ -s servername ]
DESCRIPTION
The dkserver program identifies itself to the data switch network as being willing to accept service requests.
dkserver satisfies those requests by spawning new processes and invoking programs based on the parameters
given by the request. The response to each service request is based on how the dialstring and identity of the
caller match entries in the controltab [see srvtab(4)]. Information on how to map the users of remote hosts
into their local identities is kept in the uidfile [see dkuidtab(4)] maintained by the authorize(1M) program.
dkserver saves the values of the environment variables at the time it is started and selectively passes them
along in the initial environment of all commands invoked. See the description of the –e argument and the
section on environment variables for more details.
dkserver maintains a log file of all incoming requests in logfile which should be cleaned out periodically.
You should check this file for lines containing the tokens ERROR or DENIED which will indicate conditions
that may need administrative attention.
The default action when no options are specified is to start dkserver on the first hardware interface using the
machine’s nodename [see uname(2)] with default values for the logfile, verbosity level, and controltab.
The default action of dkserver may be altered by the specification of one or more of the following command
line arguments:
–i interface Use interface instead of the first hardware interface (interface 0). The interface should be
specified as a numeric digit (for example, 1) If this option is omitted and the environment
variable DKINTF is set, dkserver will start the interface using the value of DKINTF. If
this option is used, the value for DKINTF will be ignored.
–s servername Use servername for the name of the server instead of the nodename retrieved from the
uname(2) system call.
-v verbosity The verbosity parameter controls the amount of information recorded to the logfile about
each incoming call. The range of values is 1 to 9 (default 6) where increasing the value
results in progressively more log detail. An invalid specification of verbosity will be
rounded to the nearest legitimate value (that is, values less than 1 will be rounded to 1 and
values greater than 9 will be rounded to 9). See the manual page for dksrvlog(4) for
information on the content of the logfile.
–c controltab The directory or file controltab should be used as the dkserver control table instead of the
default directory /etc/opt/dk/srvtab. The full pathname for controltab must be specified.
[See srvtab(4).]
–u uidfile The file uidfile should be used to map the users of remote hosts into their local identities
instead of the default file /etc/opt/dk/dkuidtab . The full pathname for uidfile must be
specified. [See dkuidtab(4).]
–e Expand the base environment variables to include DKINTF and merge them with the
current environment. This expanded environment will be passed as the initial environment
of all commands invoked. See the section on environment variables for more details.
–S The logfile is made secure; only readable by root. The default permission of logfile, as
created by the dkserver, allows reading by everyone. The logfile will only be readable by
root if this option is specified. However, the dkserver will not change the permission of
an existing logfile if this option is not used.