|
|
1.1 root 1: .../files
2:
3: This directory contains the support files needed for INGRES to
4: run. The critical ones are:
5:
6: dayfile7
7: The dayfile printed by the tty monitor when INGRES starts
8: up.
9: dbtmplt7
10: The file that describes the database, used by creatdb.
11: equel7
12: The process table used by INGRES when called from an EQUEL
13: program.
14: error7_0
15: error7_1
16: error7_2
17: error7_3
18: error7_4
19: error7_5
20: error7_6
21: The files containing the text of error messages.
22: proctab7
23: The process table used by INGRES when it is invoked normally.
24: procx7
25: The process talbe used by INGRES when it is invoked
26: as "ingresx".
27: startup
28: A file executed by the monitor at startup, typically
29: defining a few basic macros.
30: usage
31: A file printed if the parameters to INGRES are wrong.
32: This can be as terse or as verbose as necessary, given the
33: sophistication of your users.
34: users
35: A list of valid INGRES users, their internal code, and
36: their capabilities. More below.
37:
38: Every user on your system who is going to use INGRES \must/ be
39: included in the "users" file. This file looks much like the
40: /etc/passwd file, with fields separated by colons, etc. The
41: first, third, and fourth fields are the login name, user id,
42: and group ids respectively, exactly like the /etc/passwd file.
43: The second field is that user's internal code, which is always
44: exactly two printable characters. There is also an octal field
45: that describes capabilities; the principle capability is the
46: 000001 bit which allows that person to create databases.
47:
48: Users that are not entered into the users file WILL NOT be
49: able to use INGRES.
50:
51: This file can be set up for everyone on your system by using
52: the "usersetup" command.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.