|
|
1.1 root 1: .th USERSETUP UNIX 3/14/79
2: .sh NAME
3: usersetup \- setup users file
4: .sh SYNOPSIS
5: .bd \&.../bin/usersetup
6: [ flags [ pathname ] ]
7: .sh DESCRIPTION
8: The
9: .bd /etc/passwd
10: file
11: is read
12: and reformatted to become
13: the \*(II users file,
14: stored into
15: .bd \&.../files/users.
16: If
17: .it pathname
18: is specified,
19: it replaces ``...''.
20: If pathname is ``\c
21: .bd \-\c
22: \&'',
23: the result is written to the standard output.
24: .s3
25: The user name, user, and group id's
26: are initialized to be identical to the corresponding entry
27: in the
28: .bd /etc/passwd
29: file.
30: The status field is initialized to be 000001,
31: except for user
32: .bd ingres,
33: which is initialized to all permission bits set.
34: If the
35: .it status
36: parameter is provided,
37: the field is set to this instead.
38: The ``initialization file'' parameter
39: is set to the file
40: .bd \&.ingres
41: in the user's login directory.
42: The user code field is initialized
43: with sequential two-character codes.
44: All other fields are initialized
45: to be null.
46: .s3
47: After running
48: .it usersetup,
49: the
50: .bd users
51: file must be edited.
52: Any users who are to have any special authorizations
53: should have the status field changed,
54: according to the specifications
55: in users(files).
56: To disable a user from executing \*(II entirely,
57: completely remove her line
58: from the users file.
59: .s3
60: As \*(UU users
61: are added or deleted
62: from the
63: .bd /etc/passwd
64: file,
65: the
66: .bd users
67: file will need to be editted
68: to reflect the changes.
69: For deleted users,
70: it is only necessary
71: to delete the line for that user
72: from the
73: .bd users
74: file.
75: To add a user,
76: you must assign that user a code
77: in the form "aa"
78: and enter a line in the users file
79: in the form:
80: .br
81: name:cc:uid:gid:status:flags:proctab:initfile::databases
82: .br
83: where
84: .it name
85: is the user name
86: (taken from the first field of the
87: .bd /etc/passwd
88: file
89: entry for this user),
90: .it cc
91: is the user code assigned,
92: which must be exactly two characters long
93: and must not be the same as any other existing user codes,
94: .it uid
95: and
96: .it gid
97: are the user and group ids
98: (taken from the third and fourth fields
99: in the
100: .bd /etc/passwd
101: entry),
102: .it status
103: is the status bits for this user,
104: normally 000000,
105: .it flags
106: are the default flags
107: for \*(II
108: (on a per-user basis),
109: .it proctab
110: is the default process table
111: for this user
112: (which defaults to
113: .bd =proctab7\c
114: ),
115: and
116: .it databases
117: is a list of the databases
118: this user may enter.
119: If null,
120: she may use all databases.
121: If the first character is a dash
122: (``\-''),
123: the field is a comma separated list
124: of databases
125: which she may not enter.
126: Otherwise,
127: it is a list
128: of databases
129: which she may enter.
130: .s3
131: The
132: .it databases
133: field
134: includes the names of databases
135: which may be created.
136: .s3
137: .it Usersetup
138: may be executed only once,
139: to initially create the
140: .bd users
141: file.
142: .sh FILES
143: \&.../files/users
144: .br
145: \&/etc/passwd
146: .sh "SEE ALSO"
147: ingres(unix),
148: passwd(V),
149: users(files)
150: .sh BUGS
151: It should be able to bring the
152: .bd users
153: file
154: up to date.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.