|
|
1.1 root 1: The connection server is made up of a number of intertwined programs.
2: These programs are roughly divided into three groups:
3: 1) Managers (/usr/ipc/mgrs/*) -- These are non-terminating programs started
4: by /etc/rc. One group consists of dialers that listen for and place calls on
5: particular networks (dkmgr, tcpmgr, tpcmgr, udpmgr). The next group are
6: programs used to configure the different networks (dkhup, kdiload, ipconfig,
7: dkipconfig, routed). Finally is the service manager (svcmgr) that offers
8: the standard user services such as login and program execution.
9: 2) Commands (/usr/ipc/bin/*) -- These programs are run by users to perform
10: network functions such as remote login and remote executions.
11: 3) Servers (/usr/ipc/servers/*) -- These are programs started by `svcmgr'
12: when called by a command on some other system (telnetd, Rpush, Rpull).
13: These programs have been shipped to all of our systems.
14:
15: Connection service programs communicate using streams. They rendezvous by
16: mounting onto files in the directory /cs. A /cs has been shipped to all our
17: systems. It is protected to be writable only by root and bin. This ensures
18: that unprivileged users may not usurp rendezvous points. A number of user
19: accessable moutn points (tcp.1024-tcp.1124) exist for use by telnet and ftp.
20:
21: Configuration files are needed by `svcmgr' to know what services to
22: offer and for whom to offer them. These are the files /usr/ipc/lib/auth,
23: /usr/ipc/lib/auth.local, /usr/ipc/lib/serv, and /usr/ipc/lib/serv.local.
24: /usr/ipc/lib/auth and /usr/ipc/lib/serv are shipped from bowell and contain
25: the base set of services and authentications. The *.local files should NEVER
26: be shipped. They take precedence over the base set and are used to configure
27: system peculiarities.
28:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.