NIO CommKit Host Interface Installation and System Administration Manual

SRVTAB(4) SRVTAB(4)
E-78 CommKit Host Interface, Release 4.0
NAME
srvtab – dkserver(1M) control file format
DESCRIPTION
This file format is used by the dkserver(1M) program to obtain information on how to process incoming call
requests. The format consists of one or more lines, each with exactly six fields. The lines are kept in a number
of files in the srvtab directory. The default directory is /etc/opt/dk/srvtab. The file to be searched is located
by the incoming Service name (for example, /etc/opt/dk/srvtab/login is the name of the file used for the login
service). If no file exists for a specific service, then the catch-all file’*’ is used.
Each time a call is processed by dkserver(1M), it scans the appropriate srvtab file for the first match with
certain fields in the incoming call request information. If no match is found, the call is denied. If a match is
found, the remaining fields indicate which program to execute, what arguments to pass to it, etc. The fields
which participate in the match are the System, Service, and User fields. The Flag field may also be used to
limit the scope of the service (see Flag below).
Any line that has a leading # character is a comment line. All other lines are control lines.
The control lines consist of the following fields delimited by tabs:
Note: Delimit fields by tabs only. Do not use blanks.
System: Originating Group name pattern: area/exchange/group[!][.user]. Originating group
patterns may be completely specified, or contain embedded asterisks and/or question
marks.
Each embedded asterisk matches any set of zero or more characters and each embedded
question mark matches any single character. For example, area6/e*/???? matches only 4-
character groups in area area6 whose exchange begins with the letter e; the patterns *,
*/*, and */*/* are equivalent and match all originating groups.
If the last character in the pattern is a !, then the pattern does not match the dkserver(1M)
name. For example, if the local server name is hostx, area6/exch2/*! matches all groups
in area area6 and exchange exch2 except for area6/exch2/hostx. This feature can be used
to prevent users from calling themselves.
NOTE: The server name of the host and the Originating Group name of its interface on the
AT&T data switch must be assigned the same value for the ! feature to be effective.
Specification of the optional .user field allows selection/restriction of services to certain
users. The .user field is the decimal value of the ID of the user on the originating host.
Service: The specific service requested, (that is, the string which appears after the period in the
dialstring). The special entry – matches the null service (that is, the case where no specific
service is requested). A single asterisk functions as a service wildcard which will match any
requested service. The following services exist by convention; others may be added as
needed by the application.
- Null service (generally login)
* Wildcard service (matches any requested service)
login Login
do Invoke commands on remote hosts
rl Remote login
pupu File transfer (for example, push/pull)
rx Remote execution
uucp Uucp handler
authorize Invoke authorize(1M) on remote hosts