| blob | e5de56c1dc798602d1ee22583d10a2d5421e9e49 |
1 '\" te
2 .\" Copyright 2014 Nexenta Systems, Inc. All rights reserved.
3 .\" Copyright 1989 AT&T.
4 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved.
5 .\" Portions Copyright (c) 1992, X/Open Company Limited All Rights Reserved
6 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at http://www.opengroup.org/bookstore/.
7 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text
8 .\" are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical
9 .\" and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
10 .\" This notice shall appear on any product containing this material.
11 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
12 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
13 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
14 .TH CHMOD 1 "Nov 24, 2014"
15 .SH NAME
16 chmod \- change the permissions mode of a file
17 .SH SYNOPSIS
18 .LP
19 .nf
20 \fBchmod\fR [\fB-fR\fR] \fIabsolute-mode\fR \fIfile\fR...
21 .fi
23 .LP
24 .nf
25 \fBchmod\fR [\fB-fR\fR] \fIsymbolic-mode-list\fR \fIfile\fR...
26 .fi
28 .LP
29 .nf
30 \fBchmod\fR [\fB-fR\fR] \fIacl_operation\fR \fIfile\fR...
31 .fi
33 .LP
34 .nf
35 \fBchmod\fR [\fB-fR\fR] [\fB-@\fR \fInamed_attribute\fR]...\fIattribute_specification_list\fR \fIfile\fR...
36 .fi
38 .SH DESCRIPTION
39 .LP
40 The \fBchmod\fR utility changes or assigns the mode of a file.
41 .sp
42 .LP
43 \fBchmod\fR can also be used to modify Access Control Lists (ACLs) on files and
44 directories, and to modify boolean read-write system attributes on regular
45 files, directories, and opaque extended attribute files.
46 .SS "Absolute Mode"
47 .LP
48 An absolute mode command line has the following format:
49 .sp
50 .LP
51 \fBchmod\fR [\fIoptions\fR] \fIabsolute-mode\fR \fIfile\fR . . .
52 .sp
53 .LP
54 where \fIabsolute-mode\fR is specified using octal numbers \fInnnn\fR defined
55 as follows:
56 .sp
57 .ne 2
58 .na
59 \fB\fIn\fR\fR
60 .ad
61 .RS 5n
62 a number from \fB0\fR to \fB7\fR. An absolute mode is constructed from the OR
63 of any of the following modes:
64 .sp
65 .ne 2
66 .na
67 \fB\fB4000\fR\fR
68 .ad
69 .RS 12n
70 Set user \fBID\fR on execution.
71 .RE
73 .sp
74 .ne 2
75 .na
76 \fB\fB20\fR\fI\|#\|\fR\fB0\fR\fR
77 .ad
78 .RS 12n
79 Set group \fBID\fR on execution if \fI#\fR is \fB7\fR, \fB5\fR, \fB3\fR, or
80 \fB1\fR.
81 .sp
82 Enable mandatory locking if \fI#\fR is \fB6\fR, \fB4\fR, \fB2\fR, or \fB0\fR.
83 .sp
84 For directories, files are created with BSD semantics for propagation of the
85 group ID. With this option, files and subdirectories created in the directory
86 inherit the group ID of the directory, rather than of the current process. For
87 directories, the set-gid bit can only be set or cleared by using symbolic mode.
88 .RE
90 .sp
91 .ne 2
92 .na
93 \fB\fB1000\fR\fR
94 .ad
95 .RS 12n
96 Turn on sticky bit. See \fBchmod\fR(2).
97 .RE
99 .sp
100 .ne 2
101 .na
102 \fB\fB0400\fR\fR
103 .ad
104 .RS 12n
105 Allow read by owner.
106 .RE
108 .sp
109 .ne 2
110 .na
111 \fB\fB0200\fR\fR
112 .ad
113 .RS 12n
114 Allow write by owner.
115 .RE
117 .sp
118 .ne 2
119 .na
120 \fB\fB0100\fR\fR
121 .ad
122 .RS 12n
123 Allow execute (search in directory) by owner.
124 .RE
126 .sp
127 .ne 2
128 .na
129 \fB\fB0700\fR\fR
130 .ad
131 .RS 12n
132 Allow read, write, and execute (search) by owner.
133 .RE
135 .sp
136 .ne 2
137 .na
138 \fB\fB0040\fR\fR
139 .ad
140 .RS 12n
141 Allow read by group.
142 .RE
144 .sp
145 .ne 2
146 .na
147 \fB\fB0020\fR\fR
148 .ad
149 .RS 12n
150 Allow write by group.
151 .RE
153 .sp
154 .ne 2
155 .na
156 \fB\fB0010\fR\fR
157 .ad
158 .RS 12n
159 Allow execute (search in directory) by group.
160 .RE
162 .sp
163 .ne 2
164 .na
165 \fB\fB0070\fR\fR
166 .ad
167 .RS 12n
168 Allow read, write, and execute (search) by group.
169 .RE
171 .sp
172 .ne 2
173 .na
174 \fB\fB0004\fR\fR
175 .ad
176 .RS 12n
177 Allow read by others.
178 .RE
180 .sp
181 .ne 2
182 .na
183 \fB\fB0002\fR\fR
184 .ad
185 .RS 12n
186 Allow write by others.
187 .RE
189 .sp
190 .ne 2
191 .na
192 \fB\fB0001\fR\fR
193 .ad
194 .RS 12n
195 Allow execute (search in directory) by others.
196 .RE
198 .sp
199 .ne 2
200 .na
201 \fB\fB0007\fR\fR
202 .ad
203 .RS 12n
204 Allow read, write, and execute (search) by others.
205 .RE
207 .RE
209 .sp
210 .LP
211 For directories, the \fBsetgid\fR bit cannot be set (or cleared) in absolute
212 mode; it must be set (or cleared) in symbolic mode using \fBg+s\fR (or
213 \fBg-s\fR).
214 .SS "Symbolic Mode"
215 .LP
216 A symbolic mode command line has the following format:
217 .sp
218 .LP
219 \fBchmod\fR [\fIoptions\fR] \fIsymbolic-mode-list\fR \fIfile\fR . . .
220 .sp
221 .LP
222 where \fIsymbolic-mode-list\fR is a comma-separated list (with no intervening
223 white space) of symbolic mode expressions of the form:
224 .sp
225 .LP
226 [\fBwho\fR] \fIoperator\fR [\fIpermissions\fR]
227 .sp
228 .LP
229 Operations are performed in the order given. Multiple \fIpermissions\fR letters
230 following a single operator cause the corresponding operations to be performed
231 simultaneously.
232 .sp
233 .ne 2
234 .na
235 \fB\fBwho\fR\fR
236 .ad
237 .RS 14n
238 zero or more of the characters \fBu\fR, \fBg\fR, \fBo\fR, and \fBa\fR
239 specifying whose permissions are to be changed or assigned:
240 .sp
241 .ne 2
242 .na
243 \fB\fBu\fR\fR
244 .ad
245 .RS 5n
246 user's permissions
247 .RE
249 .sp
250 .ne 2
251 .na
252 \fB\fBg\fR\fR
253 .ad
254 .RS 5n
255 group's permissions
256 .RE
258 .sp
259 .ne 2
260 .na
261 \fB\fBo\fR\fR
262 .ad
263 .RS 5n
264 others' permissions
265 .RE
267 .sp
268 .ne 2
269 .na
270 \fB\fBa\fR\fR
271 .ad
272 .RS 5n
273 all permissions (user, group, and other)
274 .RE
276 If \fBwho\fR is omitted, it defaults to \fBa\fR, but the setting of the file
277 mode creation mask (see \fBumask\fR in \fBsh\fR(1) or \fBcsh\fR(1) for more
278 information) is taken into account. When \fBwho\fR is omitted, \fBchmod\fR does
279 not override the restrictions of your user mask.
280 .RE
282 .sp
283 .ne 2
284 .na
285 \fB\fIoperator\fR\fR
286 .ad
287 .RS 14n
288 either \fB+\fR, \fB\(mi\fR, or \fB=\fR, signifying how permissions are to be
289 changed:
290 .sp
291 .ne 2
292 .na
293 \fB\fB+\fR\fR
294 .ad
295 .RS 8n
296 Add permissions.
297 .sp
298 If \fIpermissions\fR are omitted, nothing is added.
299 .sp
300 If \fBwho\fR is omitted, add the file mode bits represented by
301 \fIpermissions\fR, \fIexcept\fR for the those with corresponding bits in the
302 file mode creation mask.
303 .sp
304 If \fBwho\fR is present, add the file mode bits represented by the
305 \fIpermissions\fR.
306 .RE
308 .sp
309 .ne 2
310 .na
311 \fB\fB\(mi\fR\fR
312 .ad
313 .RS 8n
314 Take away permissions.
315 .sp
316 If \fIpermissions\fR are omitted, do nothing.
317 .sp
318 If \fBwho\fR is omitted, clear the file mode bits represented by
319 \fIpermissions\fR, \fIexcept\fR for those with corresponding bits in the file
320 mode creation mask.
321 .sp
322 If \fBwho\fR is present, clear the file mode bits represented by
323 \fIpermissions\fR.
324 .RE
326 .sp
327 .ne 2
328 .na
329 \fB\fB=\fR\fR
330 .ad
331 .RS 8n
332 Assign permissions absolutely.
333 .sp
334 If \fBwho\fR is omitted, clear all file mode bits; if \fBwho\fR is present,
335 clear the file mode bits represented by \fBwho\fR.
336 .sp
337 If \fIpermissions\fR are omitted, do nothing else.
338 .sp
339 If \fBwho\fR is omitted, add the file mode bits represented by
340 \fIpermissions\fR, \fIexcept\fR for the those with corresponding bits in the
341 file mode creation mask.
342 .sp
343 If \fBwho\fR is present, add the file mode bits represented by
344 \fIpermissions\fR.
345 .RE
347 Unlike other symbolic operations, \fB=\fR has an absolute effect in that it
348 resets all other bits represented by \fBwho\fR. Omitting \fIpermissions\fR is
349 useful only with \fB=\fR to take away all permissions.
350 .RE
352 .sp
353 .ne 2
354 .na
355 \fB\fIpermission\fR\fR
356 .ad
357 .RS 14n
358 any compatible combination of the following letters:
359 .sp
360 .ne 2
361 .na
362 \fB\fBl\fR\fR
363 .ad
364 .RS 9n
365 mandatory locking
366 .RE
368 .sp
369 .ne 2
370 .na
371 \fB\fBr\fR\fR
372 .ad
373 .RS 9n
374 read permission
375 .RE
377 .sp
378 .ne 2
379 .na
380 \fB\fBs\fR\fR
381 .ad
382 .RS 9n
383 user or group set-ID
384 .RE
386 .sp
387 .ne 2
388 .na
389 \fB\fBt\fR\fR
390 .ad
391 .RS 9n
392 sticky bit
393 .RE
395 .sp
396 .ne 2
397 .na
398 \fB\fBw\fR\fR
399 .ad
400 .RS 9n
401 write permission
402 .RE
404 .sp
405 .ne 2
406 .na
407 \fB\fBx\fR\fR
408 .ad
409 .RS 9n
410 execute permission
411 .RE
413 .sp
414 .ne 2
415 .na
416 \fB\fBX\fR\fR
417 .ad
418 .RS 9n
419 execute permission if the file is a directory or if there is execute permission
420 for one of the other user classes
421 .RE
423 .sp
424 .ne 2
425 .na
426 \fB\fBu\fR,\fBg\fR,\fBo\fR\fR
427 .ad
428 .RS 9n
429 indicate that \fIpermission\fR is to be taken from the current user, group or
430 other mode respectively.
431 .RE
433 Permissions to a file can vary depending on your user identification number
434 (UID) or group identification number (GID). Permissions are described in three
435 sequences each having three characters:
436 .sp
438 .sp
439 .TS
440 l l l
441 l l l .
442 User Group Other
443 rwx rwx rwx
444 .TE
446 This example (user, group, and others all have permission to read, write, and
447 execute a given file) demonstrates two categories for granting permissions: the
448 access class and the permissions themselves.
449 .sp
450 The letter \fBs\fR is only meaningful with \fBu\fR or \fBg\fR, and \fBt\fR only
451 works with \fBu\fR.
452 .sp
453 Mandatory file and record locking (\fBl\fR) refers to a file's ability to have
454 its reading or writing permissions locked while a program is accessing that
455 file.
456 .sp
457 In a directory which has the set-group-ID bit set (reflected as either
458 \fB-----s---\fR or \fB-----l---\fR in the output of \fB\&'ls -ld'\fR), files
459 and subdirectories are created with the group-ID of the parent directory\(emnot
460 that of current process.
461 .sp
462 It is not possible to permit group execution and enable a file to be locked on
463 execution at the same time. In addition, it is not possible to turn on the
464 set-group-ID bit and enable a file to be locked on execution at the same time.
465 The following examples, therefore, are invalid and elicit error messages:
466 .sp
467 .in +2
468 .nf
469 chmod g+x,+l \fIfile\fR
470 chmod g+s,+l \fIfile\fR
471 .fi
472 .in -2
473 .sp
475 Only the owner of a file or directory (or the super-user) can change that
476 file's or directory's mode. Only the super-user can set the sticky bit on a
477 non-directory file. If you are not super-user, \fBchmod\fR masks the sticky-bit
478 but does not return an error. In order to turn on a file's set-group-ID bit,
479 your own group ID must correspond to the file's and group execution must be
480 set.
481 .RE
483 .SS "ACL Operation"
484 .LP
485 An ACL Operation command line has the following format:
486 .sp
487 .in +2
488 .nf
489 chmod [\fIoptions\fR] A[\fInumber\fR]- \fIfile\fR ...
490 chmod [\fIoptions\fR] A-\fIacl_specification\fR \fIfile\fR ...
491 chmod [\fIoptions\fR] A[\fIindex\fR]{+|=}\fIacl_specification\fR \fIfile\fR ...
492 .fi
493 .in -2
494 .sp
496 .sp
497 .LP
498 Where \fIacl_specification\fR is a comma-separated list (with no intervening
499 white space) of an ACL specification of the form:
500 .sp
501 .ne 2
502 .na
503 \fB\fBA[\fIindex\fR]+\fIacl_specification\fR\fR\fR
504 .ad
505 .RS 30n
506 Prepends the access control entries (ACE) specified in \fIacl_specification\fR
507 to the beginning of the file's ACL. Depending on the file system, the ACL can
508 be reordered when applied to the file. If "optional" number is specified then
509 new ACEs are inserted before specified number.
510 .RE
512 .sp
513 .ne 2
514 .na
515 \fB\fBA-\fR\fR
516 .ad
517 .RS 30n
518 Removes all ACEs for current ACL on file and replaces current ACL with new ACL
519 that represents only the current mode of the file.
520 .RE
522 .sp
523 .ne 2
524 .na
525 \fB\fBA\fIindex\fR\fR-\fR
526 .ad
527 .RS 30n
528 Removes ACE specified by \fIindex\fR number.
529 .RE
531 .sp
532 .ne 2
533 .na
534 \fB\fBA-\fIacl_specification\fR\fR\fR
535 .ad
536 .br
537 .na
538 \fB\fR
539 .ad
540 .RS 30n
541 Removes ACEs specified by \fIacl_specification\fR, if they exist in current
542 file's ACL.
543 .RE
545 .sp
546 .ne 2
547 .na
548 \fB\fBA=\fIacl_specification\fR\fR\fR
549 .ad
550 .RS 30n
551 Replaces a files entire ACL with \fIacl_specification\fR.
552 .RE
554 .sp
555 .ne 2
556 .na
557 \fB\fBA[\fIindex\fR]=\fIacl_specification\fR\fR\fR
558 .ad
559 .RS 30n
560 Replaces ACEs starting at a specific index number in the current ACL on the
561 file. If multiple ACEs are specified, then each subsequent ACE in
562 \fIacl_specification\fR replaces the corresponding ACE in the current ACL.
563 .RE
565 .sp
566 .LP
567 \fBPOSIX-draft ACL Specification (as supported by UFS)\fR
568 .sp
569 .LP
570 POSIX-draft ACLs (as supported by UFS) are specified as colon (\fB:\fR)
571 separated fields of the following.
572 .sp
573 .ne 2
574 .na
575 \fBuser::perms\fR
576 .ad
577 .sp .6
578 .RS 4n
579 File owner permissions.
580 .RE
582 .sp
583 .ne 2
584 .na
585 \fBuser:\fIusername\fR:perms\fR
586 .ad
587 .sp .6
588 .RS 4n
589 Permissions for a specific user.
590 .RE
592 .sp
593 .ne 2
594 .na
595 \fBgroup::perms\fR
596 .ad
597 .sp .6
598 .RS 4n
599 File group owner permissions.
600 .RE
602 .sp
603 .ne 2
604 .na
605 \fBgroup:\fIgroupname:\fRperms\fR
606 .ad
607 .sp .6
608 .RS 4n
609 Permissions for a specific group.
610 .RE
612 .sp
613 .ne 2
614 .na
615 \fBother::perms\fR
616 .ad
617 .sp .6
618 .RS 4n
619 Permissions for user other than the file owner or members of file group owner.
620 .RE
622 .sp
623 .ne 2
624 .na
625 \fBmask:perms\fR
626 .ad
627 .sp .6
628 .RS 4n
629 The ACL mask. The mask entry specifies the maximum permissions allowed for user
630 (other than that the owner) and for groups.
631 .RE
633 .sp
634 .ne 2
635 .na
636 \fBdefault:user::perms\fR
637 .ad
638 .sp .6
639 .RS 4n
640 Default file owner permissions.
641 .RE
643 .sp
644 .ne 2
645 .na
646 \fBdefault:user:\fIusername\fR:perms\fR
647 .ad
648 .sp .6
649 .RS 4n
650 Default permissions for a specific user.
651 .RE
653 .sp
654 .ne 2
655 .na
656 \fBdefault:group::perms\fR
657 .ad
658 .sp .6
659 .RS 4n
660 Default file group owner permissions.
661 .RE
663 .sp
664 .ne 2
665 .na
666 \fBdefault:group:\fIgroupname\fR:perms\fR
667 .ad
668 .sp .6
669 .RS 4n
670 Default permissions for a specific group.
671 .RE
673 .sp
674 .ne 2
675 .na
676 \fBdefault:other:perms\fR
677 .ad
678 .sp .6
679 .RS 4n
680 Default permissions for user other than the file owner or members of the file
681 group owner.
682 .RE
684 .sp
685 .ne 2
686 .na
687 \fBdefault:mask:perms\fR
688 .ad
689 .sp .6
690 .RS 4n
691 Default ACL mask.
692 .RE
694 .sp
695 .LP
696 The above specification allows for ACLs to be specified such as:
697 .sp
698 .in +2
699 .nf
700 user:tom:rw-,mask:rwx,group:staff:r-x
701 .fi
702 .in -2
703 .sp
705 .sp
706 .LP
707 \fBNFSv4 ACL Specification (as supported by NFSv4 and ZFS)\fR
708 .sp
709 .LP
710 NFSv4 ACLs provide richer ACL semantics. They provide both allow and deny
711 entries, finer grained permissions, and enhanced inheritance control.
712 .sp
713 .LP
714 NFSv4 ACLs are specified as colon (\fB:\fR) separated fields of the following.
715 .sp
716 .ne 2
717 .na
718 \fBowner@:<perms>[:inheritance flags]:<allow|deny>\fR
719 .ad
720 .sp .6
721 .RS 4n
722 Permissions for file owner.
723 .RE
725 .sp
726 .ne 2
727 .na
728 \fBgroup@:<perms>[:inheritance flags]:<allow|deny>\fR
729 .ad
730 .sp .6
731 .RS 4n
732 Permissions for file group owner.
733 .RE
735 .sp
736 .ne 2
737 .na
738 \fBeveryone@:<perms>[:inheritance flags]:<allow|deny>\fR
739 .ad
740 .sp .6
741 .RS 4n
742 Permissions for everyone, including file owner and group owner.
743 .RE
745 .sp
746 .ne 2
747 .na
748 \fBuser:<username>:<perms>[:inheritance flags]:<allow|deny>\fR
749 .ad
750 .sp .6
751 .RS 4n
752 Permissions for a specific user.
753 .RE
755 .sp
756 .ne 2
757 .na
758 \fBusersid:<sid string>:<perms>[:inheritance flags]:<allow|deny>\fR
759 .ad
760 .sp .6
761 .RS 4n
762 Permissions for a specific user, but user is specified by SID.
763 .RE
765 .sp
766 .ne 2
767 .na
768 \fBgroup:<groupname>:<perms>[:inheritance flags]:<allow|deny>\fR
769 .ad
770 .sp .6
771 .RS 4n
772 Permissions for a specific group.
773 .RE
775 .sp
776 .ne 2
777 .na
778 \fBgroupsid:<sid string>:<perms>[:inheritance flags]:<allow|deny>\fR
779 .ad
780 .sp .6
781 .RS 4n
782 Permissions for a specific group, but group is specified by SID.
783 .RE
785 .sp
786 .ne 2
787 .na
788 \fBsid:<sid string>:<perms>[:inheritance flags]:<allow|deny>\fR
789 .ad
790 .sp .6
791 .RS 4n
792 Permissions for a specific SID, but it doesn't matter if it is a user or a
793 group.
794 .RE
796 .sp
797 .LP
798 Permissions can be specified in three different \fBchmod\fR ACL formats:
799 verbose, compact, or positional. The verbose format uses words to indicate that
800 the permissions are separated with a forward slash (\fB/\fR) character. Compact
801 format uses the permission letters and positional format uses the permission
802 letters or the hyphen (\fB-\fR) to identify no permissions.
803 .sp
804 .LP
805 The permissions for verbose mode and their abbreviated form in parentheses for
806 compact and positional mode are described as follows:
807 .sp
808 .ne 2
809 .na
810 \fBread_data (\fBr\fR)\fR
811 .ad
812 .RS 24n
813 Permission to read the data of a file.
814 .RE
816 .sp
817 .ne 2
818 .na
819 \fBlist_directory (\fBr\fR)\fR
820 .ad
821 .RS 24n
822 Permission to list the contents of a directory.
823 .RE
825 .sp
826 .ne 2
827 .na
828 \fBwrite_data (\fBw\fR)\fR
829 .ad
830 .RS 24n
831 Permission to modify a file's data. anywhere in the file's offset range.
832 .RE
834 .sp
835 .ne 2
836 .na
837 \fBadd_file (\fBw\fR)\fR
838 .ad
839 .RS 24n
840 Permission to add a new file to a directory.
841 .RE
843 .sp
844 .ne 2
845 .na
846 \fBappend_data (\fBp\fR)\fR
847 .ad
848 .RS 24n
849 The ability to modify a file's data, but only starting at EOF.
850 .sp
851 Currently, this permission is not supported.
852 .RE
854 .sp
855 .ne 2
856 .na
857 \fBadd_subdirectory (\fBp\fR)\fR
858 .ad
859 .RS 24n
860 Permission to create a subdirectory to a directory.
861 .RE
863 .sp
864 .ne 2
865 .na
866 \fBread_xattr (\fBR\fR)\fR
867 .ad
868 .RS 24n
869 Ability to read the extended attributes of a file.
870 .RE
872 .sp
873 .ne 2
874 .na
875 \fBwrite_xattr (\fBW\fR)\fR
876 .ad
877 .RS 24n
878 Ability to create extended attributes or write to the extended attribute
879 directory.
880 .RE
882 .sp
883 .ne 2
884 .na
885 \fBexecute (\fBx\fR)\fR
886 .ad
887 .RS 24n
888 Permission to execute a file.
889 .RE
891 .sp
892 .ne 2
893 .na
894 \fBread_attributes (\fBa\fR)\fR
895 .ad
896 .RS 24n
897 The ability to read basic attributes (non-ACLs) of a file.
898 .RE
900 .sp
901 .ne 2
902 .na
903 \fBwrite_attributes (\fBA\fR)\fR
904 .ad
905 .RS 24n
906 Permission to change the times associated with a file or directory to an
907 arbitrary value.
908 .RE
910 .sp
911 .ne 2
912 .na
913 \fBdelete (\fBd\fR)\fR
914 .ad
915 .RS 24n
916 Permission to delete a file.
917 .RE
919 .sp
920 .ne 2
921 .na
922 \fBdelete_child (\fBD\fR)\fR
923 .ad
924 .RS 24n
925 Permission to delete a file within a directory.
926 .RE
928 .sp
929 .ne 2
930 .na
931 \fBread_acl (\fBc\fR)\fR
932 .ad
933 .RS 24n
934 Permission to read the ACL of a file.
935 .RE
937 .sp
938 .ne 2
939 .na
940 \fBwrite_acl (\fBC\fR)\fR
941 .ad
942 .RS 24n
943 Permission to write the ACL of a file.
944 .RE
946 .sp
947 .ne 2
948 .na
949 \fBwrite_owner (\fBo\fR)\fR
950 .ad
951 .RS 24n
952 Permission to change the owner of a file.
953 .RE
955 .sp
956 .ne 2
957 .na
958 \fBsynchronize (\fBs\fR)\fR
959 .ad
960 .RS 24n
961 Permission to access file locally at server with synchronize reads and writes.
962 .sp
963 Currently, this permission is not supported.
964 .RE
966 .sp
967 .LP
968 Using the compact ACL format, permissions are specified by using 14 unique
969 letters to indicate permissions.
970 .sp
971 .LP
972 Using the positional ACL format, permissions are specified as positional
973 arguments similar to the \fBls\fR \fB-V\fR format. The hyphen (\fB-\fR), which
974 indicates that no permission is granted at that position, can be omitted and
975 only the required letters have to be specified.
976 .sp
977 .LP
978 The letters above are listed in the order they would be specified in positional
979 notation.
980 .sp
981 .LP
982 Permissions can be specified with these letters in the following way:
983 .sp
984 .in +2
985 .nf
986 rwx--D--------
987 .fi
988 .in -2
989 .sp
991 .sp
992 .LP
993 The hyphens can be removed to compact the string as follows:
994 .sp
995 .in +2
996 .nf
997 rwxD
998 .fi
999 .in -2
1000 .sp
1002 .sp
1003 .LP
1004 Several special permission sets or aliases are also supported. The following
1005 permission sets are used the same way that verbose permissions are specified.
1006 .sp
1007 .ne 2
1008 .na
1009 \fB\fBfull_set\fR\fR
1010 .ad
1011 .RS 14n
1012 All permissions.
1013 .RE
1015 .sp
1016 .ne 2
1017 .na
1018 \fB\fBmodify_set\fR\fR
1019 .ad
1020 .RS 14n
1021 All permissions except \fBwrite_acl\fR and \fBwrite_owner\fR.
1022 .RE
1024 .sp
1025 .ne 2
1026 .na
1027 \fB\fBread_set\fR\fR
1028 .ad
1029 .RS 14n
1030 \fBread_data, read_acl, read_attributes,\fR and \fBread_xattr\fR.
1031 .RE
1033 .sp
1034 .ne 2
1035 .na
1036 \fB\fBwrite_set\fR\fR
1037 .ad
1038 .RS 14n
1039 \fBwrite_data, append_data, write_attributes\fR, and \fBwrite_xattr\fR
1040 .RE
1042 .sp
1043 .LP
1044 The optional inheritance flags can be specified in the three formats. The first
1045 format uses words to indicate the various inheritance flags separated with a
1046 forward slash (\fB/\fR) character.
1047 .sp
1048 .ne 2
1049 .na
1050 \fBfile_inherit (\fBf\fR)\fR
1051 .ad
1052 .RS 20n
1053 Inherit to all newly created files.
1054 .RE
1056 .sp
1057 .ne 2
1058 .na
1059 \fBdir_inherit (\fBd\fR)\fR
1060 .ad
1061 .RS 20n
1062 Inherit to all newly created directories.
1063 .RE
1065 .sp
1066 .ne 2
1067 .na
1068 \fBinherit_only (\fBi\fR)\fR
1069 .ad
1070 .RS 20n
1071 When placed on a directory, do not apply to the directory, only to newly
1072 created files and directories. This flag requires that either
1073 \fBfile_inherit\fR and or \fBdir_inherit\fR is also specified.
1074 .RE
1076 .sp
1077 .ne 2
1078 .na
1079 \fBno_propagate (\fBn\fR)\fR
1080 .ad
1081 .RS 20n
1082 Indicates that ACL entries should be inherited to objects in a directory, but
1083 inheritance should stop after descending one level. This flag is dependent upon
1084 either \fBfile_inherit\fR and or \fBdir_inherit\fR also being specified.
1085 .RE
1087 .sp
1088 .LP
1089 The inheritance flags listed can also be specified in the compact format or as
1090 positional arguments similar to the \fBls\fR \fB-V\fR format. A hyphen
1091 character indicates that the inheritance flag at that position is not specified
1092 in the positional ACL format.
1093 .sp
1094 .LP
1095 The inheritance flags can be specified with these letters in any of the
1096 following equivalent ways.
1097 .sp
1098 .in +2
1099 .nf
1100 file_inherit/dir_inherit/no_propagate
1101 .fi
1102 .in -2
1103 .sp
1105 .sp
1106 .in +2
1107 .nf
1108 fd-n--
1109 .fi
1110 .in -2
1111 .sp
1113 .sp
1114 .in +2
1115 .nf
1116 fdn
1117 .fi
1118 .in -2
1119 .sp
1121 .sp
1122 .LP
1123 With this inheritance model, an ACL entry can be specified such as:
1124 .sp
1125 .in +2
1126 .nf
1127 user:tom:read_data/write_data/read_attributes:file_inherit:allow
1128 user:fred:read_data:file_inherit/dir_inherit:deny
1129 user:bob:read_data:allow
1130 .fi
1131 .in -2
1132 .sp
1134 .SS "Attribute Operation"
1135 .LP
1136 An attribute operation command line has the following format:
1137 .sp
1138 .in +2
1139 .nf
1140 chmod [\fIoptions\fR] \fIattribute_specification_list\fR \fIfile\fR ...
1141 .fi
1142 .in -2
1143 .sp
1145 .sp
1146 .LP
1147 where \fIattribute_specification_list\fR is the character \fBS\fR followed by a
1148 comma-separated list of one or more \fIattribute_specifications\fR. Each
1149 \fIattribute_specification\fR is of the form:
1150 .sp
1151 .in +2
1152 .nf
1153 [\fIoperator\fR]\fIattribute_specifier\fR
1154 .fi
1155 .in -2
1156 .sp
1158 .sp
1159 .LP
1160 An \fIoperator\fR is one of the following:
1161 .sp
1162 .ne 2
1163 .na
1164 \fB\fB+\fR\fR
1165 .ad
1166 .RS 5n
1167 Each attribute specified by the associated \fIattribute_specifier\fR is
1168 adjusted to match the value specified by the \fIattribute_specifier\fR.
1169 .RE
1171 .sp
1172 .ne 2
1173 .na
1174 \fB\fB-\fR\fR
1175 .ad
1176 .RS 5n
1177 Each attribute specified by the associated \fIattribute_specifier\fR is
1178 adjusted to match the inverse of the value specified by the
1179 \fIattribute_specifier\fR.
1180 .RE
1182 .sp
1183 .ne 2
1184 .na
1185 \fB\fB=\fR\fR
1186 .ad
1187 .RS 5n
1188 Each attribute specified by the associated \fIattribute_specifier\fR is
1189 adjusted to match the value specified by the \fIattribute_specifier\fR. Any
1190 boolean read-write extended system attributes associated with the current file
1191 that are not specified by \fIattribute_specifier\fR is cleared.
1192 .RE
1194 .sp
1195 .LP
1196 If an \fIoperator\fR is not specified in an \fIattribute_specification\fR,
1197 \fBchmod\fR behaves as if \fB+\fR had been specified.
1198 .sp
1199 .LP
1200 An \fIattribute_specifier\fR takes one of the following forms:
1201 .sp
1202 .ne 2
1203 .na
1204 \fB\fBa\fR\fR
1205 .ad
1206 .sp .6
1207 .RS 4n
1208 Set all boolean read-write extended system attributes associated with the
1209 current file.
1210 .RE
1212 .sp
1213 .ne 2
1214 .na
1215 \fB\fBc[\fIcompact_attribute_list\fR]\fR\fR
1216 .ad
1217 .br
1218 .na
1219 \fB\fBc'{'\fIcompact_attribute_list\fR'}'\fR\fR
1220 .ad
1221 .sp .6
1222 .RS 4n
1223 Set each boolean read-write extended system attribute identified by
1224 \fIcompact_attribute_list\fR.
1225 .RE
1227 .sp
1228 .ne 2
1229 .na
1230 \fB\fBv[\fIverbose_attribute_setting\fR]\fR\fR
1231 .ad
1232 .br
1233 .na
1234 \fB\fBv['{'\fIverbose_attribute_setting_list\fR'}']\fR\fR
1235 .ad
1236 .sp .6
1237 .RS 4n
1238 Set each boolean read-write extended system attribute identified by
1239 \fIverbose_attribute_setting\fR.
1240 .RE
1242 .sp
1243 .LP
1244 A \fIcompact_attribute_list\fR is a list of zero or more adjacent attribute
1245 abbreviation characters from list of \fBAttribute Names and Abbreviation
1246 Characters\fR later in this section. An arbitrary number of hyphen (\fB-\fR)
1247 characters can be included in a \fIcompact_attribute_list\fR. These are
1248 ignored.
1249 .sp
1250 .LP
1251 A \fIverbose_attribute_setting\fR is an attribute name from the list of
1252 \fBAttribute Names and Abbreviation Characters\fR later in this section,
1253 optionally, immediately preceded by \fBno\fR. If the attribute name is used
1254 without \fBno\fR, the attribute is set; otherwise the attribute is cleared.
1255 .sp
1256 .LP
1257 A \fIverbose_attribute_setting_list\fR is zero or more comma-separated
1258 \fIverbose_attribute_setting\fRs.
1259 .sp
1260 .LP
1261 Multiple operations specified for a file are accumulated and are all set for a
1262 file operand as a single attribute setting operation. If an attribute is
1263 specified more than once in an \fIattribute_specification_list\fR, the last
1264 specified operation is applied.
1265 .sp
1266 .LP
1267 The following is a list of \fBAttribute Names and Abbreviation Characters\fR:
1268 .sp
1269 .ne 2
1270 .na
1271 \fB\fBAttribute Name\fR\fR
1272 .ad
1273 .RS 18n
1274 \fBAbbreviation Character\fR
1275 .RE
1277 .sp
1278 .ne 2
1279 .na
1280 \fB\fBhidden\fR\fR
1281 .ad
1282 .RS 18n
1283 \fBH\fR
1284 .RE
1286 .sp
1287 .ne 2
1288 .na
1289 \fB\fBsystem\fR\fR
1290 .ad
1291 .RS 18n
1292 \fBS\fR
1293 .RE
1295 .sp
1296 .ne 2
1297 .na
1298 \fB\fBreadonly\fR\fR
1299 .ad
1300 .RS 18n
1301 \fBR\fR
1302 .RE
1304 .sp
1305 .ne 2
1306 .na
1307 \fB\fBarchive\fR\fR
1308 .ad
1309 .RS 18n
1310 \fBA\fR
1311 .RE
1313 .sp
1314 .ne 2
1315 .na
1316 \fB\fBnounlink\fR\fR
1317 .ad
1318 .RS 18n
1319 \fBu\fR
1320 .RE
1322 .sp
1323 .ne 2
1324 .na
1325 \fB\fBimmutable\fR\fR
1326 .ad
1327 .RS 18n
1328 \fBi\fR
1329 .RE
1331 .sp
1332 .ne 2
1333 .na
1334 \fB\fBappendonly\fR\fR
1335 .ad
1336 .RS 18n
1337 \fBa\fR
1338 .RE
1340 .sp
1341 .ne 2
1342 .na
1343 \fB\fBnodump\fR\fR
1344 .ad
1345 .RS 18n
1346 \fBd\fR
1347 .RE
1349 .sp
1350 .ne 2
1351 .na
1352 \fB\fBav_quarantined\fR\fR
1353 .ad
1354 .RS 18n
1355 \fBq\fR
1356 .RE
1358 .sp
1359 .ne 2
1360 .na
1361 \fB\fBav_modified\fR\fR
1362 .ad
1363 .RS 18n
1364 \fBm\fR
1365 .RE
1367 .sp
1368 .ne 2
1369 .na
1370 \fB\fBoffline\fR\fR
1371 .ad
1372 .RS 18n
1373 \fBO\fR
1374 .RE
1376 .sp
1377 .ne 2
1378 .na
1379 \fB\fBsparse\fR\fR
1380 .ad
1381 .RS 18n
1382 \fBs\fR
1383 .RE
1385 .SH OPTIONS
1386 .LP
1387 The following options are supported:
1388 .sp
1389 .ne 2
1390 .na
1391 \fB\fB-f\fR\fR
1392 .ad
1393 .RS 22n
1394 Force. \fBchmod\fR does not complain if it fails to change the mode of a file.
1395 .RE
1397 .sp
1398 .ne 2
1399 .na
1400 \fB\fB-R\fR\fR
1401 .ad
1402 .RS 22n
1403 Recursively descend through directory arguments, setting the mode for each
1404 file. When symbolic links are encountered, the mode of the target file is
1405 changed, but no recursion takes place.
1406 .RE
1408 .sp
1409 .ne 2
1410 .na
1411 \fB\fB-@\fR \fInamed_attribute\fR\fR
1412 .ad
1413 .RS 22n
1414 Perform the attribute operation on the named extended attribute file of each
1415 file operand instead of the file operand itself. If multiple \fB-@\fR
1416 operations are supplied, the attribute specification mode is applied to each of
1417 the named attribute files.
1418 .sp
1419 A named attribute of \fB*\fR carries meaning to \fBchmod\fR, and is considered
1420 to mean all extended attribute files associated with a file operand. This does
1421 not refer to the special files \fB\&.\fR and \fB\&..\fR.
1422 .sp
1423 A named attribute of \fB\&..\fR carries special meaning to \fBchmod\fR, and is
1424 considered to mean the file operand itself. This allows \fBchmod\fR, in a
1425 single call, to apply the attribute specification mode to the specified named
1426 attribute file of the file operand and the file operand itself.
1427 .RE
1429 .SH OPERANDS
1430 .LP
1431 The following operands are supported:
1432 .sp
1433 .ne 2
1434 .na
1435 \fB\fIabsolute-mode\fR\fR
1436 .ad
1437 .br
1438 .na
1439 \fB\fIsymbolic-mode-list\fR\fR
1440 .ad
1441 .sp .6
1442 .RS 4n
1443 Represents the change to be made to the file mode bits of each file named by
1444 one of the \fIfile\fR operands. See \fBAbsolute Mode\fR and \fBSymbolic Mode\fR
1445 in the \fBDESCRIPTION\fR section of this manual page for more information.
1446 .RE
1448 .sp
1449 .ne 2
1450 .na
1451 \fB\fIacl_operation\fR\fR
1452 .ad
1453 .sp .6
1454 .RS 4n
1455 Represents the modification to be performed on the file's ACL. See \fBACL
1456 Operation\fR in the \fBDESCRIPTION\fR section for more information.
1457 .sp
1458 \fIacl_operation\fR is one of the following:
1459 .sp
1460 .in +2
1461 .nf
1462 \fBA[\fR\fInumber\fR\fB] -\fR
1463 \fBA-\fR\fIacl_specification\fR
1464 \fBA[\fR\fIindex\fR\fB]{+|=}\fR\fBacl_specification\fR
1465 .fi
1466 .in -2
1467 .sp
1469 .RE
1471 .sp
1472 .ne 2
1473 .na
1474 \fB\fIattribute_specification_list\fR\fR
1475 .ad
1476 .sp .6
1477 .RS 4n
1478 Represents the modification to performed on the file's attributes. See
1479 Attribute Operation in the \fBDESCRIPTION\fR section of this manual page for
1480 more information.
1481 .RE
1483 .sp
1484 .ne 2
1485 .na
1486 \fB\fIfile\fR\fR
1487 .ad
1488 .sp .6
1489 .RS 4n
1490 A path name of a file whose file mode bits are to be modified.
1491 .RE
1493 .SH USAGE
1494 .LP
1495 See \fBlargefile\fR(5) for the description of the behavior of \fBchmod\fR when
1496 encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
1497 .SH EXAMPLES
1498 .LP
1499 \fBExample 1 \fRDenying \fBexecute\fR Permission
1500 .sp
1501 .LP
1502 The following example denies execute permission to everyone:
1504 .sp
1505 .in +2
1506 .nf
1507 % chmod a-x \fIfile\fR
1508 .fi
1509 .in -2
1510 .sp
1512 .LP
1513 \fBExample 2 \fRAllowing \fBread-only\fR Permission
1514 .sp
1515 .LP
1516 The following example allows only read permission to everyone:
1518 .sp
1519 .in +2
1520 .nf
1521 % chmod 444 \fIfile\fR
1522 .fi
1523 .in -2
1524 .sp
1526 .LP
1527 \fBExample 3 \fRMaking a File \fBreadable\fR and \fBwritable\fR
1528 .sp
1529 .LP
1530 The following example makes a file readable and writable by the group and
1531 others:
1533 .sp
1534 .in +2
1535 .nf
1536 % chmod go+rw \fIfile\fR
1537 % chmod 066 \fIfile\fR
1538 .fi
1539 .in -2
1540 .sp
1542 .LP
1543 \fBExample 4 \fRLocking a File From Access
1544 .sp
1545 .LP
1546 The following example locks a file from access:
1548 .sp
1549 .in +2
1550 .nf
1551 $ chmod +l \fIfile\fR
1552 .fi
1553 .in -2
1554 .sp
1556 .LP
1557 \fBExample 5 \fRGranting \fBread\fR, \fBwrite\fR, \fBexecute\fR, and \fBset
1558 group-ID\fR Permission on a File
1559 .sp
1560 .LP
1561 The following example grants everyone read, write, and execute permissions on
1562 the file, and turns on the set group-ID:
1564 .sp
1565 .in +2
1566 .nf
1567 $ chmod a=rwx,g+s \fIfile\fR
1568 $ chmod 2777 \fIfile\fR
1569 .fi
1570 .in -2
1571 .sp
1573 .LP
1574 \fBExample 6 \fRPrepending a New ACL Entry on a ZFS File
1575 .sp
1576 .LP
1577 The following example prepends a new ACL entry on a ZFS file.
1579 .sp
1580 .LP
1581 First, display the current ACL:
1583 .sp
1584 .in +2
1585 .nf
1586 $ ls -v file.3
1587 -rw-r--r-- 1 marks staff 0 Oct 9 15:49 file.3
1588 0:owner@:execute:deny
1589 1:owner@:read_data/write_data/append_data/write_xattr/
1590 write_attributes/write_acl/write_owner:allow
1591 2:group@:write_data/append_data/execute:deny
1592 3:group@:read_data:allow
1593 4:everyone@:write_data/append_data/write_xattr/execute/
1594 write_attributes/write_acl/write_owner:deny
1595 5:everyone@:read_data/read_xattr/read_attributes/read_acl/
1596 synchronize:allow
1597 .fi
1598 .in -2
1599 .sp
1601 .sp
1602 .LP
1603 Issue the following command:
1605 .sp
1606 .in +2
1607 .nf
1608 $ chmod A+user:lp:read_data:deny file.3
1609 .fi
1610 .in -2
1611 .sp
1613 .sp
1614 .LP
1615 Display the new ACL:
1617 .sp
1618 .in +2
1619 .nf
1620 $ ls -v file.3
1621 -rw-r--r--+ 1 marks staff 0 Oct 9 15:49 file.3
1622 0:user:lp:read_data:deny
1623 1:owner@:execute:deny
1624 2:owner@:read_data/write_data/append_data/write_xattr/
1625 write_attributes/write_acl/write_owner:allow
1626 3:group@:write_data/append_data/execute:deny
1627 4:group@:read_data:allow
1628 5:everyone@:write_data/append_data/write_xattr/execute/
1629 write_attributes/write_acl/write_owner:deny
1630 6:everyone@:read_data/read_xattr/read_attributes/read_acl/
1631 synchronize:allow
1632 .fi
1633 .in -2
1634 .sp
1636 .LP
1637 \fBExample 7 \fRPrepending a New POSIX-draft ACL Entry on a UFS File
1638 .sp
1639 .LP
1640 The following example prepends a new POSIX-draft ACL entry on a UFS file.
1642 .sp
1643 .LP
1644 First, display the current ACL:
1646 .sp
1647 .in +2
1648 .nf
1649 $ ls -v file.2
1650 -rw-r--r-- 1 marks staff 0 Oct 9 15:52 file.2
1651 0:user::rw-
1652 1:group::r-- #effective:r--
1653 2:mask:r--
1654 3:other:r--
1655 .fi
1656 .in -2
1657 .sp
1659 .sp
1660 .LP
1661 Issue the following command:
1663 .sp
1664 .in +2
1665 .nf
1666 $ chmod A+user:lp:-wx file.2
1667 .fi
1668 .in -2
1669 .sp
1671 .sp
1672 .LP
1673 Display the new ACL:
1675 .sp
1676 .in +2
1677 .nf
1678 $ ls -v file.2
1679 -rw-r--r--+ 1 marks staff 0 Oct 9 15:52 file.2
1680 0:user::rw-
1681 1:user:lp:-wx #effective:---
1682 2:group::r-- #effective:r--
1683 3:mask:r--
1684 4:other:r--
1685 .fi
1686 .in -2
1687 .sp
1689 .LP
1690 \fBExample 8 \fRInserting an ACL Entry in a Specific Position on a ZFS file
1691 .sp
1692 .LP
1693 The following example inserts an ACL entry in a specific position on a ZFS file
1694 system. It also illustrates the compact ACL format.
1696 .sp
1697 .LP
1698 First, display the ACL to pick a location to insert a new ACE.
1700 .sp
1701 .in +2
1702 .nf
1703 % ls -V file.1
1704 -rw-r--r--+ 1 root root 0 Oct 6 12:16 file.1
1705 user:lp:rw------------:------:allow
1706 owner@:--x-----------:------:deny
1707 owner@:rw-p---A-W-Co-:------:allow
1708 group@:-wxp----------:------:deny
1709 group@:r-------------:------:allow
1710 everyone@:-wxp---A-W-Co-:------:deny
1711 everyone@:r-----a-R-c--s:------:allow
1712 .fi
1713 .in -2
1714 .sp
1716 .sp
1717 .LP
1718 Next, insert a new entry in location 3. This causes the entries that are
1719 currently in position 3 - 6 to be pushed down.
1721 .sp
1722 .LP
1723 Issue the following command:
1725 .sp
1726 .in +2
1727 .nf
1728 $ chmod A3+user:marks:r:deny file.1
1729 .fi
1730 .in -2
1731 .sp
1733 .sp
1734 .LP
1735 Display the new ACL:
1737 .sp
1738 .in +2
1739 .nf
1740 $ ls -V file.1
1741 -rw-r--r--+ 1 root staff 0 Feb 3 14:13 file.1
1742 user:lp:rw------------:------:allow
1743 owner@:--x-----------:------:deny
1744 owner@:rw-p---A-W-Co-:------:allow
1745 user:marks:r-------------:------:deny
1746 group@:-wxp----------:------:deny
1747 group@:r-------------:------:allow
1748 everyone@:-wxp---A-W-Co-:------:deny
1749 everyone@:r-----a-R-c--s:------:allow
1750 .fi
1751 .in -2
1752 .sp
1754 .LP
1755 \fBExample 9 \fRInserting a POSIX-draft ACL in a Specific Position on a UFS
1756 File
1757 .sp
1758 .LP
1759 The file system reorders ACLs when they are stored in the file system. The
1760 following example illustrates this behavior.
1762 .sp
1763 .in +2
1764 .nf
1765 $ ls -v file.1
1766 -rw-r--r--+ 1 root root 0 Sep 29 16:10 file.1
1767 0:user::rw-
1768 1:user:lp:rw- #effective:r--
1769 2:group::r-- #effective:r--
1770 3:mask:r--
1771 4:other:r--
1772 .fi
1773 .in -2
1774 .sp
1776 .sp
1777 .LP
1778 Now, insert an entry at index position 3. The command works, but the file
1779 system reorders the ACL.
1781 .sp
1782 .in +2
1783 .nf
1784 $ chmod A3+user:marks:rw- file.1
1785 $ ls -v file.1
1786 -rw-r--r--+ 1 root root 0 Sep 29 16:10 file.1
1787 0:user::rw-
1788 1:user:lp:rw- #effective:r--
1789 2:user:marks:rw- #effective:r--
1790 3:group::r-- #effective:r--
1791 4:mask:r--
1792 5:other:r--
1793 .fi
1794 .in -2
1795 .sp
1797 .sp
1798 .LP
1799 Rather than inserting the ACL entry in position 3 as requested, it actually
1800 ends up in position 2.
1802 .LP
1803 \fBExample 10 \fRRemoving an ACL Entry on a ZFS File
1804 .sp
1805 .LP
1806 The following example removes the \fBlp\fR entry from an ACL:
1808 .sp
1809 .in +2
1810 .nf
1811 $ ls -v file.3
1812 -rw-r--r--+ 1 marks staff 0 Oct 9 15:49 file.3
1813 0:user:lp:read_data:deny
1814 1:owner@:execute:deny
1815 2:owner@:read_data/write_data/append_data/write_xattr/
1816 write_attributes/write_acl/write_owner:allow
1817 3:group@:write_data/append_data/execute:deny
1818 4:group@:read_data:allow
1819 5:everyone@:write_data/append_data/write_xattr/execute/
1820 write_attributes/write_acl/write_owner:deny
1821 6:everyone@:read_data/read_xattr/read_attributes/read_acl/
1822 synchronize:allow
1823 .fi
1824 .in -2
1825 .sp
1827 .sp
1828 .in +2
1829 .nf
1830 $ chmod A-user:lp:read_data:deny file.3
1831 $ ls -v file.3
1832 -rw-r--r-- 1 marks staff 0 Oct 9 15:49 file.3
1833 0:owner@:execute:deny
1834 1:owner@:read_data/write_data/append_data/write_xattr/
1835 write_attributes/write_acl/write_owner:allow
1836 2:group@:write_data/append_data/execute:deny
1837 3:group@:read_data:allow
1838 4:everyone@:write_data/append_data/write_xattr/execute/
1839 write_attributes/write_acl/write_owner:deny
1840 5:everyone@:read_data/read_xattr/read_attributes/read_acl/
1841 synchronize:allow
1842 .fi
1843 .in -2
1844 .sp
1846 .LP
1847 \fBExample 11 \fRRemoving a POSIX-draft ACL on a UFS File
1848 .sp
1849 .LP
1850 The following example removes the \fBlp\fR entry from an ACL:
1852 .sp
1853 .in +2
1854 .nf
1855 $ ls -v file.2
1856 -rw-r--r--+ 1 marks staff 0 Oct 9 15:52 file.2
1857 0:user::rw-
1858 1:user:lp:-wx #effective:---
1859 2:group::r-- #effective:r--
1860 3:mask:r--
1861 4:other:r--
1862 .fi
1863 .in -2
1864 .sp
1866 .sp
1867 .in +2
1868 .nf
1869 $ chmod A-user:lp:-wx file.2
1870 $ ls -v file.2
1871 -rw-r--r-- 1 marks staff 0 Oct 9 15:52 file.2
1872 0:user::rw-
1873 1:group::r-- #effective:r--
1874 2:mask:r--
1875 3:other:r--
1876 .fi
1877 .in -2
1878 .sp
1880 .LP
1881 \fBExample 12 \fRRemoving a Specific ACL Entry by Index Number on a ZFS File
1882 .sp
1883 .LP
1884 Consider the following ACL:
1886 .sp
1887 .in +2
1888 .nf
1889 $ ls -v file
1890 0:group:staff:read_data/write_data/execute/read_acl:allow
1891 1:user:bin:read_data:deny
1892 2:user:bin:read_data:allow
1893 3:owner@:write_data/append_data:deny
1894 4:owner@:read_data/write_xattr/execute/write_attributes/write_acl
1895 /write_owner:allow
1896 5:group@:write_data/append_data:deny
1897 6:group@:read_data/execute:allow
1898 7:everyone@:write_data/append_data/write_xattr/write_attributes
1899 /write_acl/write_owner:deny
1900 8:everyone@:read_data/read_xattr/execute/read_attributes/read_acl
1901 /synchronize:allow
1902 .fi
1903 .in -2
1904 .sp
1906 .sp
1907 .LP
1908 Remove the second user entry for bin.
1910 .sp
1911 .in +2
1912 .nf
1913 $ chmod A2- file
1914 $ ls -v file
1915 0:group:staff:read_data/write_data/execute/read_acl:allow
1916 1:user:bin:read_data:deny
1917 2:owner@:write_data/append_data:deny
1918 3:owner@:read_data/write_xattr/execute/write_attributes/write_acl
1919 /write_owner:allow
1920 4:group@:write_data/append_data:deny
1921 5:group@:read_data/execute:allow
1922 6:everyone@:write_data/append_data/write_xattr/write_attributes
1923 /write_acl/write_owner:deny
1924 7:everyone@:read_data/read_xattr/execute/read_attributes/read_acl
1925 /synchronize:allow
1926 .fi
1927 .in -2
1928 .sp
1930 .LP
1931 \fBExample 13 \fRRemoving a Specific POSIX-draft ACL Entry on a UFS File
1932 .sp
1933 .LP
1934 The following example removes the lp entry by index number from the following
1935 ACL:
1937 .sp
1938 .in +2
1939 .nf
1940 $ ls -v file.1
1941 -rw-r--r--+ 1 root root 0 Sep 29 16:10 file.1
1942 0:user::rw-
1943 1:user:lp:rw- #effective:r--
1944 2:group::r-- #effective:r--
1945 3:mask:r--
1946 4:other:r--
1948 $ chmod A1- file.1
1949 $ ls -v
1950 -rw-r--r--+ 1 root root 0 Sep 29 16:10 file.1
1951 0:user::rw-
1952 1:group::r-- #effective:r--
1953 2:mask:r--
1954 3:other:r--
1955 .fi
1956 .in -2
1957 .sp
1959 .LP
1960 \fBExample 14 \fRRemoving All ACLs From a File
1961 .sp
1962 .LP
1963 The following command works with either NFSv4/ZFS or POSIX-draft ACLs.
1965 .sp
1966 .LP
1967 Consider the following ACL:
1969 .sp
1970 .in +2
1971 .nf
1972 $ ls -v file.3
1973 -rw-r--r--+ 1 marks staff 0 Oct 9 15:49 file.3
1974 0:user:lp:read_data/write_data:allow
1975 1:user:marks:read_acl:allow
1976 2:owner@:execute:deny
1977 3:owner@:read_data/write_data/append_data/write_xattr/
1978 write_attributes/write_acl/write_owner:allow
1979 4:group@:write_data/append_data/execute:deny
1980 5:group@:read_data:allow
1981 6:everyone@:write_data/append_data/write_xattr/execute/
1982 write_attributes/write_acl/write_owner:deny
1983 7:everyone@:read_data/read_xattr/read_attributes/read_acl/
1984 synchronize:allow
1985 .fi
1986 .in -2
1987 .sp
1989 .sp
1990 .LP
1991 The existing ACL is effectively removed and is replaced with an ACL that
1992 represents the permission bits of the file.
1994 .sp
1995 .in +2
1996 .nf
1997 $ chmod A- file.3
1998 $ ls -v file.3
1999 -rw-r--r-- 1 marks staff 0 Oct 9 15:49 file.3
2000 0:owner@:execute:deny
2001 1:owner@:read_data/write_data/append_data/write_xattr/
2002 write_attributes/write_acl/write_owner:allow
2003 2:group@:write_data/append_data/execute:deny
2004 3:group@:read_data:allow
2005 4:everyone@:write_data/append_data/write_xattr/execute/
2006 write_attributes/write_acl/write_owner:deny
2007 5:everyone@:read_data/read_xattr/read_attributes/read_acl/
2008 synchronize:allow
2009 .fi
2010 .in -2
2011 .sp
2013 .LP
2014 \fBExample 15 \fRReplacing an Entire ACL Entry on a ZFS File
2015 .sp
2016 .LP
2017 Use the following \fBchmod\fR syntax if you want to replace an ACL in its
2018 entirety:
2020 .sp
2021 .in +2
2022 .nf
2023 $ chmod A=owner@:read_data/write_data:allow,group@:read_data/
2024 write_data:allow,user:lp:read_data:allow file.4
2025 $ ls -v file.4
2026 -rw-rw----+ 1 marks staff 0 Oct 9 16:12 file.4
2027 0:owner@:read_data/write_data:allow
2028 1:group@:read_data/write_data:allow
2029 2:user:lp:read_data:allow
2030 .fi
2031 .in -2
2032 .sp
2034 .LP
2035 \fBExample 16 \fRReplacing an Entire POSIX-draft ACL on a UFS File
2036 .sp
2037 .LP
2038 This operation is a little more complicated. The replacement ACL needs the
2039 necessary entries to represent the file owner, file group owner, other, mask
2040 and any additional entries you wish to set.
2042 .sp
2043 .in +2
2044 .nf
2045 $ chmod A=user::rw-,group::rw-,other::---,mask:r--,
2046 user:lp:r-- file.3
2047 $ ls -v file.3
2048 -rw-r-----+ 1 root root 0 Oct 9 16:14 file.3
2049 0:user::rw-
2050 1:user:lp:r-- #effective:r--
2051 2:group::rw- #effective:r--
2052 3:mask:r--
2053 4:other:---
2054 .fi
2055 .in -2
2056 .sp
2058 .LP
2059 \fBExample 17 \fRReplacing a Specific Entry on a ZFS File
2060 .sp
2061 .LP
2062 Consider the following ACL.
2064 .sp
2065 .in +2
2066 .nf
2067 $ ls -v file.5
2068 -rw-r--r--+ 1 marks staff 0 Oct 9 16:18 file.5
2069 0:user:marks:read_data:allow
2070 1:owner@:execute:deny
2071 2:owner@:read_data/write_data/append_data/write_xattr/
2072 write_attributes/write_acl/write_owner:allow
2073 3:group@:write_data/append_data/execute:deny
2074 4:group@:read_data:allow
2075 5:everyone@:write_data/append_data/write_xattr/execute/
2076 write_attributes/write_acl/write_owner:deny
2077 6:everyone@:read_data/read_xattr/read_attributes/read_acl/
2078 synchronize:allow
2079 .fi
2080 .in -2
2081 .sp
2083 .sp
2084 .LP
2085 Now, change the allow access to a deny for user marks:
2087 .sp
2088 .in +2
2089 .nf
2090 $ chmod A0=user:marks:read_data:deny file.5
2091 $ ls -v file.5
2092 -rw-r--r--+ 1 marks staff 0 Aug 23 09:11 file.5
2093 0:user:marks:read_data:deny
2094 1:owner@:read_data/write_data/append_data/write_xattr/write_attributes
2095 /write_acl/write_owner:allow
2096 2:group@:write_data/append_data/execute:deny
2097 3:group@:read_data:allow
2098 4:everyone@:write_data/append_data/write_xattr/execute/write_attributes
2099 /write_acl/write_owner:deny
2100 5:everyone@:read_data/read_xattr/read_attributes/read_acl/synchronize
2101 :allow
2102 .fi
2103 .in -2
2104 .sp
2106 .LP
2107 \fBExample 18 \fRReplacing a Specific POSIX-draft ACL on a UFS File
2108 .sp
2109 .LP
2110 Consider the following ACL.
2112 .sp
2113 .in +2
2114 .nf
2115 $ ls -v file.4
2116 -rw-r--r--+ 1 marks staff 0 Oct 9 16:21 file.4
2117 0:user::rw-
2118 1:user:lp:rwx #effective:r--
2119 2:group::r-- #effective:r--
2120 3:mask:r--
2121 4:other:r--
2122 .fi
2123 .in -2
2124 .sp
2126 .sp
2127 .LP
2128 Now, change the permission on \fBlp\fR from \fBrwx\fR to \fBr--\fR:
2130 .sp
2131 .in +2
2132 .nf
2133 $ chmod A1=user:lp:r-- file.4
2135 $ ls -v file
2136 -rw-r--r--+ 1 marks staff 0 Oct 9 16:21 file.4
2137 0:user::rw-
2138 1:user:lp:r-- #effective:r--
2139 2:group::r-- #effective:r--
2140 3:mask:r--
2141 4:other:r--
2142 .fi
2143 .in -2
2144 .sp
2146 .LP
2147 \fBExample 19 \fRSetting ACL Inheritance Flags on a ZFS File
2148 .sp
2149 .LP
2150 You can only set inheritance flags on ZFS files. When setting ACLs on
2151 directories, several inheritance flags can be optionally set.
2153 .sp
2154 .LP
2155 Suppose you have an ACL entry for user \fBlp\fR that you want to be inherited
2156 to newly created files in a directory. First, you need to create an
2157 inheritable ACL entry on the directory:
2159 .sp
2160 .in +2
2161 .nf
2162 $ chmod A+user:lp:read_data:file_inherit:allow test.dir
2163 $ ls -dv test.dir
2164 drwxr-xr-x+ 2 marks staff 2 Aug 23 09:08 test.dir/
2165 0:user:lp:read_data:file_inherit:allow
2166 1:owner@::deny
2167 2:owner@:list_directory/read_data/add_file/write_data/add_subdirectory
2168 /append_data/write_xattr/execute/write_attributes/write_acl
2169 /write_owner:allow
2170 3:group@:add_file/write_data/add_subdirectory/append_data:deny
2171 4:group@:list_directory/read_data/execute:allow
2172 5:everyone@:add_file/write_data/add_subdirectory/append_data/write_xattr
2173 /write_attributes/write_acl/write_owner:deny
2174 6:everyone@:list_directory/read_data/read_xattr/execute/read_attributes
2175 /read_acl/synchronize:allow
2176 .fi
2177 .in -2
2178 .sp
2180 .sp
2181 .LP
2182 The \fBlp\fR entry is inherited to newly created files in the directory
2183 \fBtest.dir\fR.
2185 .sp
2186 .in +2
2187 .nf
2188 $ touch test.dir/file.test
2189 $ ls -v test.dir/file.test
2190 -rw-r--r--+ 1 marks staff 0 Oct 9 16:29 test.dir/file.test
2191 0:user:lp::deny
2192 1:user:lp:read_data:allow
2193 2:owner@:execute:deny
2194 3:owner@:read_data/write_data/append_data/write_xattr/
2195 write_attributes/write_acl/write_owner:allow
2196 4:group@:write_data/append_data/execute:deny
2197 5:group@:read_data:allow
2198 6:everyone@:write_data/append_data/write_xattr/execute/
2199 write_attributes/write_acl/write_owner:deny
2200 7:everyone@:read_data/read_xattr/read_attributes/read_acl/
2201 synchronize:allow
2202 .fi
2203 .in -2
2204 .sp
2206 .sp
2207 .LP
2208 The user \fBlp\fR entry is inherited to the newly created file. Multiple
2209 combinations of the inheritance flags can be specified. For example, if you
2210 wanted the \fBlp\fR entry to also be inherited to directories, then the
2211 following command can be used:
2213 .sp
2214 .in +2
2215 .nf
2216 $ chmod A+user:lp:read_data:file_inherit/\e
2217 dir_inherit:allow test.dir
2218 .fi
2219 .in -2
2220 .sp
2222 .LP
2223 \fBExample 20 \fRReplacing System Attributes of a ZFS File
2224 .sp
2225 .LP
2226 The following examples replace system attributes of a ZFS file:
2228 .sp
2229 .in +2
2230 .nf
2231 $ chmod S=v{archive,hidden,readonly,system,appendonly,\e
2232 nonodump,immutable,noav_modified,noav_quarantined,\e
2233 nounlink,nooffline,nosparse} file1
2234 .fi
2235 .in -2
2236 .sp
2238 .sp
2239 .LP
2240 or
2242 .sp
2243 .in +2
2244 .nf
2245 $ chmod S=c{AHRSaiu} file1
2246 .fi
2247 .in -2
2248 .sp
2250 .sp
2251 .LP
2252 or
2254 .sp
2255 .in +2
2256 .nf
2257 $ chmod S=c{AHRSa-i--u--} file1
2258 .fi
2259 .in -2
2260 .sp
2262 .sp
2263 .LP
2264 or
2266 .sp
2267 .in +2
2268 .nf
2269 $ chmod S=cAHRSaiu file1
2270 .fi
2271 .in -2
2272 .sp
2274 .sp
2275 .LP
2276 or
2278 .sp
2279 .in +2
2280 .nf
2281 $ chmod -@ '..' S=cAHRSaiu file1
2282 .fi
2283 .in -2
2284 .sp
2286 .sp
2287 .LP
2288 Assuming appropriate privileges, this results in the following system
2289 attributes of \fBfile1\fR being set: \fBarchive\fR, \fBhidden\fR,
2290 \fBreadonly\fR, \fBsystem\fR, \fBappendonly\fR, \fBimmutable\fR, and
2291 \fBnounlink\fR. Assuming appropriate privileges, the following system
2292 attributes of \fBfile1\fR are cleared: \fBnodump\fR, \fBav_modified\fR,
2293 \fBav_quarantined\fR, \fBoffline\fR, and \fBsparse\fR.
2295 .LP
2296 \fBExample 21 \fRClearing All System Attributes of a ZFS File
2297 .sp
2298 .LP
2299 The following examples clears all system attributes of a ZFS file:
2301 .sp
2302 .in +2
2303 .nf
2304 $ chmod S-a file1
2305 .fi
2306 .in -2
2307 .sp
2309 .sp
2310 .LP
2311 or
2313 .sp
2314 .in +2
2315 .nf
2316 $ chmod -@ '..' S-a file1
2317 .fi
2318 .in -2
2319 .sp
2321 .sp
2322 .LP
2323 Assuming appropriate privileges, all boolean read-write system attributes are
2324 cleared on \fBfile1\fR.
2326 .LP
2327 \fBExample 22 \fRSetting a System Attribute of a Named Attribute File of a ZFS
2328 File
2329 .sp
2330 .LP
2331 The following example sets a system attribute of a named attribute file of a
2332 ZFS file, but not of the file itself:
2334 .sp
2335 .in +2
2336 .nf
2337 $ chmod -@ myattr S+vhidden file1
2338 .fi
2339 .in -2
2340 .sp
2342 .sp
2343 .LP
2344 This results in the hidden system attribute being set for the named attribute
2345 file \fBmyattr\fR of \fBfile1\fR, but not the file itself.
2347 .LP
2348 \fBExample 23 \fRSetting a System Attribute of All Named Attribute File of a
2349 ZFS File
2350 .sp
2351 .LP
2352 The following example sets a system attribute of all named attribute files of a
2353 ZFS file, but not of the file itself:
2355 .sp
2356 .in +2
2357 .nf
2358 $ chmod -@ '*' S+a file1
2359 .fi
2360 .in -2
2361 .sp
2363 .LP
2364 \fBExample 24 \fRSetting a System Attribute of All Named Attribute Files of a
2365 ZFS File
2366 .sp
2367 .LP
2368 The following example sets a system attribute of all named attribute files of a
2369 ZFS file, as well as of the file itself:
2371 .sp
2372 .in +2
2373 .nf
2374 $ chmod -@ '..' -@ '*' S+vhidden file1
2375 .fi
2376 .in -2
2377 .sp
2379 .sp
2380 .LP
2381 This results in the hidden system attribute being set for all named attribute
2382 files of \fBfile1\fR, as well as the file itself.
2384 .LP
2385 \fBExample 25 \fRRecursively Descending Through a Directory Hierarchy
2386 .sp
2387 .LP
2388 The following example recursively descends through a directory hierarchy, and
2389 sets all system attributes of all named attribute files, the ZFS file operands,
2390 as well as of the directory itself:
2392 .sp
2393 .in +2
2394 .nf
2395 $ chmod -R -@ '..' -@ '*' S+a directory1
2396 .fi
2397 .in -2
2398 .sp
2400 .sp
2401 .LP
2402 This results in the hidden system attribute being set for all named attribute
2403 files of all regular files and directories within the directory hierarchy of
2404 \fBdirectory1\fR, as well as of \fBdirectory1\fR itself.
2406 .LP
2407 \fBExample 26 \fRSetting the \fBhidden\fR and \fBsystem\fR System Attributes of
2408 a ZFS File
2409 .sp
2410 .LP
2411 The following examples set the \fBhidden\fR and \fBsystem\fR system attributes
2412 of a ZFS file:
2414 .sp
2415 .in +2
2416 .nf
2417 $ chmod S+cHS file1
2418 .fi
2419 .in -2
2420 .sp
2422 .sp
2423 .LP
2424 or
2426 .sp
2427 .in +2
2428 .nf
2429 $ chmod S+vhidden,+vsystem file1
2430 .fi
2431 .in -2
2432 .sp
2434 .sp
2435 .LP
2436 or
2438 .sp
2439 .in +2
2440 .nf
2441 $ chmod S+v{hidden,system} file1
2442 .fi
2443 .in -2
2444 .sp
2446 .sp
2447 .LP
2448 or
2450 .sp
2451 .in +2
2452 .nf
2453 $ chmod S+c{-H-S--------} file1
2454 .fi
2455 .in -2
2456 .sp
2458 .sp
2459 .LP
2460 or
2462 .sp
2463 .in +2
2464 .nf
2465 $ chmod S-v{nohidden,nosystem} file1
2466 .fi
2467 .in -2
2468 .sp
2470 .sp
2471 .LP
2472 or
2474 .sp
2475 .in +2
2476 .nf
2477 $ chmod S-v{hidden,system},+v{hidden,system} file1
2478 .fi
2479 .in -2
2480 .sp
2482 .LP
2483 \fBExample 27 \fRClearing All System Attributes of a ZFS File
2484 .sp
2485 .LP
2486 The following example clears all system attributes of a ZFS file:
2488 .sp
2489 .in +2
2490 .nf
2491 $ chmod S-a file1
2492 .fi
2493 .in -2
2494 .sp
2496 .sp
2497 .LP
2498 or
2500 .sp
2501 .in +2
2502 .nf
2503 $ chmod S=v{} file1
2504 .fi
2505 .in -2
2506 .sp
2508 .sp
2509 .LP
2510 In the following two examples, the last attribute operation specified takes
2511 precedence.
2513 .sp
2514 .LP
2515 In this example, the replacement attribute name list (\fB{}\fR) clears all
2516 system attributes for \fBfile1\fR:
2518 .sp
2519 .in +2
2520 .nf
2521 $ chmod S+cHS,=v{} file1
2522 .fi
2523 .in -2
2524 .sp
2526 .sp
2527 .LP
2528 In this example, the clear attributes operation (\fB-a\fR) clears all system
2529 attributes of \fBfile1\fR:
2531 .sp
2532 .in +2
2533 .nf
2534 $ chmod S+vhidden,+vsystem,-a file1
2535 .fi
2536 .in -2
2537 .sp
2539 .LP
2540 \fBExample 28 \fRSetting the Values of All Boolean read-write System Attributes
2541 of a File
2542 .sp
2543 .LP
2544 The following example sets the values of all boolean read-write system
2545 attributes of a file to the same as the boolean read-write system attributes of
2546 another file:
2548 .sp
2549 .in +2
2550 .nf
2551 $ chmod S=v`ls -/v file1|sed -n '2s/.*{/{/p'` file2
2552 .fi
2553 .in -2
2554 .sp
2556 .sp
2557 .LP
2558 Assuming appropriate privileges and that \fBfile1\fR and \fBfile2\fR have the
2559 same supported system attributes, all system attributes of \fBfile1\fR that are
2560 set are also set on \fBfile2\fR. All system attributes of \fBfile1\fR that are
2561 cleared are also cleared on \fBfile2\fR.
2563 .SH ENVIRONMENT VARIABLES
2564 .LP
2565 See \fBenviron\fR(5) for descriptions of the following environment variables
2566 that affect the execution of \fBchmod\fR: \fBLANG\fR, \fBLC_ALL\fR,
2567 \fBLC_CTYPE\fR, \fBLC_MESSAGES\fR, and \fBNLSPATH\fR.
2568 .SH EXIT STATUS
2569 .LP
2570 The following exit values are returned:
2571 .sp
2572 .ne 2
2573 .na
2574 \fB\fB0\fR\fR
2575 .ad
2576 .RS 6n
2577 Successful completion.
2578 .RE
2580 .sp
2581 .ne 2
2582 .na
2583 \fB\fB>0\fR\fR
2584 .ad
2585 .RS 6n
2586 An error occurred.
2587 .RE
2589 .SH ATTRIBUTES
2590 .LP
2591 See \fBattributes\fR(5) for descriptions of the following attributes:
2592 .sp
2594 .sp
2595 .TS
2596 box;
2597 c | c
2598 l | l .
2599 ATTRIBUTE TYPE ATTRIBUTE VALUE
2600 _
2601 CSI Enabled
2602 _
2603 Interface Stability Committed
2604 .TE
2606 .SH SEE ALSO
2607 .LP
2608 \fBgetfacl\fR(1), \fBls\fR(1), \fBsetfacl\fR(1), \fBchmod\fR(2),
2609 \fBfgetattr\fR(3C), \fBacl\fR(5), \fBattributes\fR(5), \fBenviron\fR(5),
2610 \fBfsattr\fR(5), \fBlargefile\fR(5), \fBstandards\fR(5)
2611 .SH NOTES
2612 .LP
2613 Absolute changes do not work for the set-group-\fBID\fR bit of a directory. You
2614 must use \fBg+s\fR or \fBg-s\fR.
2615 .sp
2616 .LP
2617 \fBchmod\fR permits you to produce useless modes so long as they are not
2618 illegal (for instance, making a text file executable). \fBchmod\fR does not
2619 check the file type to see if mandatory locking is meaningful.
2620 .sp
2621 .LP
2622 If the filesystem is mounted with the \fInosuid\fR option, \fIsetuid\fR
2623 execution is not allowed.
2624 .sp
2625 .LP
2626 If you use \fBchmod\fR to change the file group owner permissions on a file
2627 with \fBACL\fR entries, both the file group owner permissions and the \fBACL\fR
2628 mask are changed to the new permissions. Be aware that the new \fBACL\fR mask
2629 permissions can change the effective permissions for additional users and
2630 groups who have \fBACL\fR entries on the file. Use the \fBgetfacl\fR(1) or
2631 \fBls\fR(1)command to make sure the appropriate permissions are set for all
2632 \fBACL\fR entries.