3 fs copyacl - Copies an ACL from a directory to one or more other directories
7 B<fs copyacl> B<-fromdir> <I<source directory (or DFS file)>>
8 B<-todir> <I<destination directory (or DFS file)>>+
9 [B<-clear>] [B<-id>] [B<-if>] [-help]
11 B<fs co> B<-f> <I<source directory (or DFS file)>>
12 B<-t> <I<destination directory (or DFS file)>>+
13 [B<-c>] [B<-id>] [B<-if>] [-h]
17 The fs copyacl command copies the access control list (ACL) from a source
18 directory to each specified destination directory. The source directory's
19 ACL is unchanged, and changes to the destination directory's ACL obey the
26 If an entry on the source ACL does not already exist on the destination
31 If an entry exists on both the source and destination ACLs, the
32 permissions from the source ACL entry replace the current permissions on
33 the destination ACL entry.
37 If an entry on the destination ACL has no corresponding entry on the
38 source ACL, it is removed if the B<-clear> flag is included and is
39 unchanged otherwise. In other words, if the B<-clear> flag is provided,
40 the source ACL completely replaces the destination ACL.
44 When using this command to copy ACLs between objects in DFS filespace
45 accessed via the AFS/DFS Migration Toolkit Protocol Translator, it is
46 possible to specify files, as well as directories, with the B<-fromdir>
47 and B<-todir> arguments. For more information on copying ACLs between DFS
48 directories and files, refer to the I<IBM AFS/DFS Migration Toolkit
49 Administration Guide and Reference>.
53 Do not copy ACLs between AFS and DFS files or directories. The ACL formats
60 =item B<-fromdir> <I<source directory>>
62 Specifies the source directory from which to copy the ACL. (Specifying an
63 AFS file copies its directory's ACL, but specifying a DFS file copies its
64 own ACL.) A partial pathname is interpreted relative to the current
67 =item B<-todir> <I<destination directory>>
69 Specifies each directory for which to alter the ACL to match the source
70 ACL. (Specifying an AFS file halts the command with an error, but
71 specifying a DFS file alters the file's ACL). A partial pathname is
72 interpreted relative to the current working directory.
74 Specify the read/write path to each directory (or DFS file), to avoid the
75 failure that results from attempting to change a read-only volume. By
76 convention, the read/write path is indicated by placing a period before
77 the cell name at the pathname's second level (for example,
78 C</afs/.abc.com>). For further discussion of the concept of read/write and
79 read-only paths through the filespace, see the B<fs mkmount> reference
84 Replaces the ACL of each destination directory with the source ACL.
88 Modifies the Initial Container ACL of each DFS directory named by the
89 B<-todir> argument, rather than the regular Object ACL. This argument is
90 supported only when both the source and each destination directory reside
91 in DFS and are accessed via the AFS/DFS Migration Toolkit Protocol
96 Modifies the Initial Object ACL of each DFS directory named by the
97 B<-todir> argument, rather than the regular Object ACL. This argument is
98 supported only when both the source and each destination directory reside
99 in DFS and are accessed via the AFS/DFS Migration Toolkit Protocol
104 Prints the online help for this command. All other valid options are
111 The following example command copies the current working directory's ACL
112 to its subdirectory called F<reports>. Note that the source directory's
113 ACL is unaffected. Entries on the F<reports> directory's that are not on
114 the source ACL of the current directory remain unaffected as well, because
115 the B<-clear> flag is not used.
117 % fs listacl . reports
122 Access list for reports is
129 % fs copyacl -fromdir . -todir reports
131 % fs listacl . reports
136 Access list for reports is
144 =head1 PRIVILEGE REQUIRED
146 To copy an ACL between AFS objects, the issuer must have the C<l> (lookup)
147 permission on the source directory's ACL and the C<a> (administer)
148 permission on each destination directory's ACL. If the B<-fromdir>
149 argument names a file rather than a directory, the issuer must have both
150 the C<l> and C<r> (read) permissions on the ACL of the file's directory.
152 To copy an ACL between DFS objects, the issuer must have the r permission
153 on the source directory or file's ACL and the C<c> (control) permission on
154 each destination directory or file's ACL.
162 I<IBM AFS/DFS Migration Toolkit Administration Guide and Reference>
166 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
168 This documentation is covered by the IBM Public License Version 1.0. It was
169 converted from HTML to POD by software written by Chas Williams and Russ
170 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.