Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod1 / pts_creategroup.pod.in
CommitLineData
805e021f
CE
1=head1 NAME
2
3pts_creategroup - Creates an (empty) Protection Database group entry
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10B<pts creategroup> S<<< B<-name> <I<group name>>+ >>>
11 S<<< [B<-owner> <I<owner of the group>>] >>>
12 S<<< [B<-id> <I<id (negated) for the group>>+] >>> S<<< [B<-cell> <I<cell name>>] >>>
13 [B<-noauth>] [B<-localauth>] [B<-force>] [B<-help>]
14 [B<-auth>] [B<-encrypt>] S<<< [B<-config> <I<config directory>>] >>>
15
16B<pts createg> S<<< B<-na> <I<group name>>+ >>> S<<< [B<-o> <I<owner of the group>>] >>>
17 S<<< [B<-i> <I<id (negated) for the group>>+] >>> S<<< [B<-c> <I<cell name>>] >>>
18 [B<-no>] [B<-l>] [B<-f>] [B<-h>]
19 [B<-a>] [B<-e>] S<<< [B<-co> <I<config directory>>] >>>
20
21B<pts cg> S<<< B<-na> <I<group name>>+ >>> S<<< [B<-o> <I<owner of the group>>] >>>
22 S<<< [B<-i> <I<id (negated) for the group>>+] >>> S<<< [B<-c> <I<cell name>>] >>>
23 [B<-no>] [B<-l>] [B<-f>] [B<-h>]
24 [B<-a>] [B<-e>] S<<< [B<-co> <I<config directory>>] >>>
25
26=for html
27</div>
28
29=head1 DESCRIPTION
30
31The B<pts creategroup> command creates an entry in the Protection Database
32for each group specified by the B<-name> argument. The entry records the
33issuer of the command as the group's creator, and as the group's owner
34unless the B<-owner> argument names an alternate user or group as the
35owner.
36
37There are two types of groups:
38
39=over 4
40
41=item *
42
43I<regular>, the names of which have two parts separated by a colon. The
44part before the colon names the group's owner. Any user can create such
45groups.
46
47=item *
48
49I<prefix-less>, which do not have an owner prefix. Only members of the
50system:administrators group can create prefix-less groups.
51
52=back
53
54Creating a group lowers the issuer's group-creation quota by one. This is
55true even if the B<-owner> argument is used to assign ownership to an
56alternate user or group. To display a user's group-creation quota, use the
57B<pts examine> command; to set it, use the B<pts setfields> command.
58
59AFS group ID (AFS GID) numbers are negative integers and by default the
60Protection Server assigns a GID that is one less (more negative) than the
61current value of the C<max group id> counter in the Protection Database,
62decrementing the counter by one for each group. Members of the
63system:administrators group can use the B<-id> argument to assign specific
64AFS GID numbers. If any of the specified GIDs is lower (more negative)
65than the current value of the C<max group id> counter, the counter is
66reset to that value. It is acceptable to specify a GID greater (less
67negative) than the current value of the counter, but the creation
68operation fails if an existing group already has it. To display or set the
69value of the C<max group id> counter, use the B<pts listmax> or B<pts
70setmax> command, respectively.
71
72=head1 OUTPUT
73
74The command generates the following string to confirm creation of each
75group:
76
77 group <name> has id <AFS GID>
78
79=head1 CAUTIONS
80
81Although using the B<-owner> argument to designate a machine entry as a
82group's owner does not generate an error, it is not recommended. The
83Protection Server does not extend the usual privileges of group ownership
84to users logged onto the machine.
85
86=head1 OPTIONS
87
88=over 4
89
90=item B<-name> <I<group name>>
91
92Specifies the name of each group to create. Provide a string of up to 63
93characters, which can include lowercase (but not uppercase) letters,
94numbers, and punctuation marks. A regular name includes a single colon
95(C<:>) to separate the two parts of the name; the colon cannot appear in a
96prefix-less group name.
97
98A regular group's name must have the following format:
99
100 <owner_name>:<group_name>
101
102and the <owner_name> field must reflect the actual owner of the group, as
103follows:
104
105=over 4
106
107=item *
108
109If the optional B<-owner> argument is not included, the field must match
110the AFS username under which the issuer is currently authenticated.
111
112=item *
113
114If the B<-owner> argument names an alternate AFS user, the field must
115match that AFS username.
116
117=item *
118
119If the B<-owner> argument names another regular group, the field must
120match the owning group's owner field (the part of its name before the
121colon). If the B<-owner> argument names a prefix-less group, the field
122must match the owning group's complete name.
123
124=back
125
126=item B<-owner> <I<owner of the group>>
127
128Specifies a user or group as the owner for each group, rather than the
129issuer of the command. Provide either an AFS username or the name of a
130regular or prefix-less group. An owning group must already have at least
131one member. This requirement prevents assignment of self-ownership to a
132group during its creation; use the B<pts chown> command after issuing this
133command, if desired.
134
135=item B<-id> <I<id for the group>>
136
137Specifies a negative integer AFS GID number for each group, rather than
138allowing the Protection Server to assign it. Precede the integer with a
139hyphen (C<->) to indicate that it is negative.
140
141If this argument is used and the B<-name> argument names multiple new
142groups, it is best to provide an equivalent number of AFS GIDs. The first
143GID is assigned to the first group, the second to the second group, and so
144on. If there are fewer GIDs than groups, the Protection Server assigns
145GIDs to the unmatched groups based on the C<max group id> counter. If
146there are more GIDs than groups, the excess GIDs are ignored. If any of
147the GIDs is lower (more negative) than the current value of the C<max
148group id> counter, the counter is reset to that value.
149
150=include fragments/pts-common.pod
151
152=back
153
154=head1 EXAMPLES
155
156In the following example, the user pat creates groups called
157C<pat:friends> and C<pat:colleagues>.
158
159 % pts creategroup -name pat:friends pat:colleagues
160
161The following example shows a member of the system:administrators group
162creating the prefix-less group C<staff> and assigning its ownership to the
163system:administrators group rather than to herself.
164
165 % pts creategroup -name staff -owner system:administrators
166
167In the following example, the user pat creates a group called
168C<smith:team-members>, which is allowed because the B<-owner> argument
169specifies the required value (C<smith>).
170
171 % pts creategroup -name smith:team-members -owner smith
172
173=head1 PRIVILEGE REQUIRED
174
175The issuer must belong to the system:administrators group to create
176prefix-less groups or include the B<-id> argument.
177
178To create a regular group, the issuer must
179
180=over 4
181
182=item *
183
184Be authenticated. The command fails if the B<-noauth> flag is provided.
185
186=item *
187
188Have a group-creation quota greater than zero. The B<pts examine> command
189displays this quota.
190
191=back
192
193=head1 SEE ALSO
194
195L<pts(1)>,
196L<pts_examine(1)>,
197L<pts_listmax(1)>,
198L<pts_setfields(1)>,
199L<pts_setmax(1)>
200
201=head1 COPYRIGHT
202
203IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
204
205This documentation is covered by the IBM Public License Version 1.0. It was
206converted from HTML to POD by software written by Chas Williams and Russ
207Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.