|
|
1.1 root 1: .TH DKMGR 8
2: .CT 1 sa_auto
3: .SH NAME
4: dkhup, dkmgr, dkzap \- manage Datakit interface
5: .SH SYNOPSIS
6: .B /usr/ipc/mgrs/dkhup
7: [
8: .B -N
9: .I prefix
10: ]
11: .br
12: .B /usr/ipc/mgrs/dkmgr
13: [
14: .B -N
15: .I prefix
16: ] [
17: .B -m
18: .I outname
19: ] [
20: .B -n
21: .I service
22: ]
23: .br
24: .B /usr/ipc/mgrs/dkzap
25: [
26: .B -N
27: .I prefix
28: ]
29: .SH DESCRIPTION
30: .I Dkhup
31: starts the common signaling channel protocol
32: for a Datakit interface.
33: Initially it sends several reset messages,
34: and tells the controller
35: to hang up all outstanding calls;
36: thereafter it simply keeps the signaling protocol running.
37: .PP
38: .I Dkmgr
39: receives and places Datakit calls.
40: Outbound calls may be placed by calling
41: .I ipcopen
42: .RI ( ipc (3))
43: with the
44: .I outname
45: specified by option
46: .BR -m ;
47: the default is
48: .BR dk .
49: .I Dkmgr
50: announces itself to the Datakit network
51: with the
52: .I service
53: name specified by option
54: .BR -n ;
55: the default is taken from
56: .FR /etc/whoami .
57: Inbound calls to
58: .I service
59: are connected to the local
60: .L login
61: service;
62: inbound calls to
63: Datakit address
64: .IB service . serv
65: are handed to local service
66: .IR serv .
67: .PP
68: .I Dkhup
69: and
70: .I dkmgr
71: are normally run once from
72: .IR rc (8).
73: Both programs must be running
74: to make the network available.
75: .PP
76: .I Dkzap
77: arranges for a KMC11-assisted Datakit interface
78: to be reset, reloaded, and restarted.
79: This should be done only if things are badly broken,
80: as it hangs up all existing calls through that interface.
81: .PP
82: Datakit devices are expected to have names of the form
83: .BI /dev/dk/dk nn
84: with
85: .I nn
86: a two-digit channel number.
87: If there are more than 100 channels,
88: the first digit overflows to lower-case letters:
89: channel 100 is
90: .LR a0 .
91: The common signaling control channel
92: is named
93: .BR /dev/dk/dkctl .
94: All three programs accept an option
95: .B -N
96: .I prefix
97: to change the naming convention;
98: for example,
99: .B -N /dev/kb/kb
100: means that the files have names like
101: .B /dev/kb/kb32
102: and
103: .BR /dev/kb/kbctl .
104: .PP
105: Support also exists for a less general naming convention:
106: there may be two sets of files,
107: named
108: .BI /dev/dk/dk0 nn
109: and
110: .BI /dev/dk/dk2 nn\c
111: ,
112: with control channels
113: .B /dev/dk/dkctl0
114: and
115: .BR /dev/dk/dkctl2 .
116: .I Dkhup
117: and
118: .I dkzap
119: take the extra argument
120: .B 0
121: or
122: .B 2
123: to point at one or the other of the control names.
124: A separate copy of
125: .I dkhup
126: is needed for each name.
127: .I Dkmgr
128: takes an option
129: .B -u
130: .IR c ,
131: where
132: .I c
133: is
134: .B 0
135: or
136: .B 2
137: to use one set of files,
138: or
139: .B b
140: to use both simultaneously;
141: in the latter case,
142: .I service
143: is announced to both networks.
144: This scheme is obsolete and overdue for replacement;
145: the missing piece is something to pick an interface for outcalls.
146: .PP
147: .I Dkmgr
148: records its activity in file
149: .I service
150: in directory
151: .BR /usr/ipc/log ,
152: default
153: .BR /usr/ipc/log/dk .
154: .SH FILES
155: .F /dev/dk
156: .SH "SEE ALSO"
157: .IR con (1),
158: .IR kmc (8),
159: .IR svcmgr (8),
160: .IR ipc (3)
161: .SH BUGS
162: .I Dkhup
163: should be folded into
164: .IR dkmgr ;
165: it is separate for historic reasons.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.