Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod1 / pts_rename.pod.in
CommitLineData
805e021f
CE
1=head1 NAME
2
3pts_rename - Changes the name of a Protection Database entry
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10B<pts rename> S<<< B<-oldname> <I<old name>> >>> S<<< B<-newname> <I<new name>> >>>
11 S<<< [B<-cell> <I<cell name>>] >>> [B<-noauth>] [B<-localauth>]
12 [B<-force>] [B<-help>] [B<-auth>] [B<-encrypt>]
13 S<<< [B<-config> <I<config directory>>] >>>
14
15B<pts ren> S<<< B<-o> <I<old name>> >>> S<<< B<-ne> <I<new name>> >>> S<<< [B<-c> <I<cell name>>] >>>
16 [B<-no>] [B<-l>] [B<-f>] [B<-h>] [B<-a>] [B<-e>]
17 S<<< [B<-co> <I<config directory>>] >>>
18
19=for html
20</div>
21
22=head1 DESCRIPTION
23
24The B<pts rename> command changes the name of the user, machine, or group
25entry specified by the B<-oldname> argument to the name specified by the
26B<-newname> argument. It is not possible to change a user or machine
27entry's name to look like a regular group entry's name (have a colon in
28it).
29
30Members of the system:administrators group can change a regular group name
31into a prefix-less name and vice versa. When changing a prefix-less group
32name into a regular group name or a regular group name to another regular
33group name, the owner field of the new name (the part before the colon)
34must correctly reflect the group's owner.
35
36Changing a regular group's owner with the B<pts chown> command
37automatically changes the owner field (the part before the colon) of the
38group's name, but does not change the owner field of any groups owned by
39the group. Use this command to rename those groups to a form that
40accurately reflects their ownership.
41
42=head1 CAUTIONS
43
44By convention, many aspects of an AFS user account have the same name as
45the user's Protection Database entry, including the Authentication
46Database entry, volume, and mount point. When using this command to change
47a user name, also change the names of all related entities to maintain
48consistency. For instructions, see the chapter on user accounts in the
49I<OpenAFS Administration Guide>.
50
51=head1 OPTIONS
52
53=over 4
54
55=item B<-oldname> <I<old name>>
56
57Specifies the current full name of the entry.
58
59=item B<-newname> <I<new name>>
60
61Specifies the new full name for the entry. For regular groups, the owner
62field (the part before the colon) of the new name must reflect the actual
63ownership of the group.
64
65=include fragments/pts-common.pod
66
67=back
68
69=head1 EXAMPLES
70
71The following example changes the name of the group staff, owned by the
72privileged user C<admin>, to C<admin:staff>:
73
74 % pts rename -oldname staff -newname admin:staff
75
76The following example changes the name of the group C<admin:finance> to
77the group C<finance>. The issuer must belong to the system:administrators
78group.
79
80 % pts rename -oldname admin:finance -newname finance
81
82=head1 PRIVILEGE REQUIRED
83
84To change a regular group name to a prefix-less name or vice versa, or to
85change a user or machine entry's name, the issuer must belong to the
86system:administrators group.
87
88To change a group name to a new name of the same type (regular or
89prefix-less), the issuer must own the group or belong to the
90system:administrators group.
91
92=head1 SEE ALSO
93
94L<pts(1)>,
95L<pts_chown(1)>
96
97=head1 COPYRIGHT
98
99IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
100
101This documentation is covered by the IBM Public License Version 1.0. It was
102converted from HTML to POD by software written by Chas Williams and Russ
103Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.