NAME | SYNOPSIS | DESCRIPTION | DIAGNOSTICS | MODES | EXAMPLES | BUGS | COMPATIBILITY | SEE ALSO | STANDARDS | ATTRIBUTES
The chmod utility modifies the file mode bits of the listed files as specified by the mode operand.
The options are as follows:
If the -R option is specified, symbolic links on the command line are followed. (Symbolic links encountered in the tree traversal are not followed by default.)
If the -R option is specified, all symbolic links are followed.
If the -R option is specified, no symbolic links are followed.
Change the modes of the file hierarchies rooted in the files instead of just the files themselves.
Do not display a diagnostic message if chmod could not modify the mode for file.
Cause chmod to be verbose, showing files as the mode is modified.
Symbolic links do not have modes, so unless the -H or -L option is set, chmod on a symbolic link always succeeds and has no effect. The -H, -L and -P options are ignored unless the -R option is specified. In addition, these options override each other and the command's actions are determined by the last one specified.
Only the owner of a file or the super-user is permitted to change the mode of a file.
The chmod utility exits 0 on success, and >0 if an error occurs.
Modes may be absolute or symbolic. An absolute mode is an octal number constructed from the sum of one or more of the following values:
(the set-user-ID-on-execution bit) Executable files with this bit set will run with effective uid set to the uid of the file owner. Directories with the set-user-id bit set will force all files and sub-directories created in them to be owned by the directory owner and not by the uid of the creating process, if the underlying file system supports this feature: see chmod(2POSIX) and the suiddir option to mount(1M).
(the set-group-ID-on-execution bit) Executable files with this bit set will run with effective gid set to the gid of the file owner.
(the sticky bit) When set on a directory, unprivileged users can delete and rename only those files in the directory that are owned by them, regardless of the permissions on the directory.
Allow read by owner.
Allow write by owner.
For files, allow execution by owner. For directories, allow the owner to search in the directory.
Allow read by group members.
Allow write by group members.
For files, allow execution by group members. For directories, allow group members to search in the directory.
Allow read by others.
Allow write by others.
For files, allow execution by others. For directories allow others to search in the directory.
For example, the absolute mode that permits read, write and execute by the owner, read and execute by group members, read and execute by others, and no set-uid or set-gid behaviour is 755 (400+200+100+040+010+004+001).
The symbolic mode is described by the following grammar:
mode ::= clause [, clause ...] clause ::= [who ...] [action ...] action action ::= op [perm ...] who ::= a | u | g | o op ::= + | - | = perm ::= r | s | t | w | x | X | u | g | o
The who symbols "u", "g", and "o" specify the user, group, and other parts of the mode bits, respectively. The who symbol "a" is equivalent to "ugo".
The perm symbols represent the portions of the mode bits as follows:
The read bits.
The set-user-ID-on-execution and set-group-ID-on-execution bits.
The sticky bit.
The write bits.
The execute/search bits.
The execute/search bits if the file is a directory or any of the execute/search bits are set in the original (unmodified) mode. Operations with the perm symbol ``X'' are only meaningful in conjunction with the op symbol ``+'', and are ignored in all other cases.
The user permission bits in the mode of the original file.
The group permission bits in the mode of the original file.
The other permission bits in the mode of the original file.
The op symbols represent the operation performed, as follows:
If no value is supplied for perm, the ``+'' operation has no effect. If no value is supplied for who, each permission bit specified in perm, for which the corresponding bit in the file mode creation mask is clear, is set. Otherwise, the mode bits represented by the specified who and perm values are set.
If no value is supplied for perm, the ``-'' operation has no effect. If no value is supplied for who, each permission bit specified in perm, for which the corresponding bit in the file mode creation mask is clear, is cleared. Otherwise, the mode bits represented by the specified who and perm values are cleared.
The mode bits specified by the who value are cleared, or, if no who value is specified, the owner, group and other mode bits are cleared. Then, if no value is supplied for who, each permission bit specified in perm, for which the corresponding bit in the file mode creation mask is clear, is set. Otherwise, the mode bits represented by the specified who and perm values are set.
Each clause specifies one or more operations to be performed on the mode bits, and each operation is applied to the mode bits in the order specified.
Operations upon the other permissions only (specified by the symbol ``o'' by itself), in combination with the perm symbols ``s'' or ``t'', are ignored.
make a file readable by anyone and writable by the owner only.
deny write permission to group and others.
set the read and write permissions to the usual defaults, but retain any execute permissions that are currently set.
make a directory or file searchable/executable by everyone if it is already searchable/executable by anyone.
make a file readable/executable by everyone and writable by the owner only.
clear all mode bits for group and others.
set the group bits equal to the user bits, but clear the group write bit.
There's no perm option for the naughty bits.
The -v option is non-standard and its use in scripts is not recommended.
The chmod utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compat ible with the exception of the perm symbols ``t'' and ``X'' which are not included in that standard.
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
---|---|
Interface Stability | Evolving |
NAME | SYNOPSIS | DESCRIPTION | DIAGNOSTICS | MODES | EXAMPLES | BUGS | COMPATIBILITY | SEE ALSO | STANDARDS | ATTRIBUTES