CHMOD(1) General Commands Manual CHMOD(1)
chmod - change mode
chmod [ -Rf ] mode file ...
The mode of each named file is changed according to mode, which may be absolute or symbolic. An absolute mode is an octal number con-
structed from the OR of the following modes:
4000 set user ID on execution
2000 set group ID on execution
1000 sticky bit, see chmod(2)
0400 read by owner
0200 write by owner
0100 execute (search in directory) by owner
0070 read, write, execute (search) by group
0007 read, write, execute (search) by others
A symbolic mode has the form:
[who] op permission [op permission] ...
The who part is a combination of the letters u (for user's permissions), g (group) and o (other). The letter a stands for all, or ugo. If
who is omitted, the default is a but the setting of the file creation mask (see umask(2)) is taken into account.
Op can be + to add permission to the file's mode, - to take away permission and = to assign permission absolutely (all other bits will be
Permission is any combination of the letters r (read), w (write), x (execute), X (set execute only if file is a directory or some other
execute bit is set), s (set owner or group id) and t (save text - sticky). Letters u, g, or o indicate that permission is to be taken from
the current mode. Omitting permission is only useful with = to take away all permissions.
When the -R option is given, chmod recursively descends its directory arguments setting the mode for each file as described above. When
symbolic links are encountered, their mode is not changed and they are not traversed.
If the -f option is given, chmod will not complain if it fails to change the mode on a file.
The first example denies write permission to others, the second makes a file executable by all if it is executable by anyone:
chmod o-w file
chmod +X file
Multiple symbolic modes separated by commas may be given. Operations are performed in the order specified. The letter s is only useful
with u or g.
Only the owner of a file (or the super-user) may change its mode.
ls(1), chmod(2), stat(2), umask(2), chown(8)
7th Edition May 22, 1986 CHMOD(1)
Check Out this Related Man Page
CHMOD(1) BSD General Commands Manual CHMOD(1)
chmod -- change file modes
chmod [-fhv] [-R [-H | -L | -P]] mode file ...
The chmod utility modifies the file mode bits of the listed files as specified by the mode operand.
The options are as follows:
-f Do not display a diagnostic message if chmod could not modify the mode for file, nor modify the exit status to reflect such failures.
-H 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.)
-h If the file is a symbolic link, change the mode of the link itself rather than the file that the link points to.
-L If the -R option is specified, all symbolic links are followed.
-P If the -R option is specified, no symbolic links are followed. This is the default.
-R Change the modes of the file hierarchies rooted in the files instead of just the files themselves.
-v Cause chmod to be verbose, showing filenames as the mode is modified. If the -v flag is specified more than once, the old and new
modes of the file will also be printed, in both octal and symbolic notation.
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:
4000 (the setuid bit). Executable files with this bit set will run with effective uid set to the uid of the file owner. Directo-
ries with this 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(2) and the suiddir option to
2000 (the setgid bit). Executable files with this bit set will run with effective gid set to the gid of the file owner.
1000 (the sticky bit). See chmod(2) and sticky(7).
0400 Allow read by owner.
0200 Allow write by owner.
0100 For files, allow execution by owner. For directories, allow the owner to search in the directory.
0040 Allow read by group members.
0020 Allow write by group members.
0010 For files, allow execution by group members. For directories, allow group members to search in the directory.
0004 Allow read by others.
0002 Allow write by others.
0001 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 oth-
ers, 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:
r The read bits.
s The set-user-ID-on-execution and set-group-ID-on-execution bits.
t The sticky bit.
w The write bits.
x The execute/search bits.
X 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
u The user permission bits in the original mode of the file.
g The group permission bits in the original mode of the file.
o The other permission bits in the original mode of the 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 (see umask(2)) is clear, is set. Otherwise, the mode bits repre-
sented 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
Operations upon the other permissions only (specified by the symbol ``o'' by itself), in combination with the perm symbols ``s'' or ``t'',
The ``w'' permission on directories will permit file creation, relocation, and copy into that directory. Files created within the directory
itself will inherit its group ID.
644 make a file readable by anyone and writable by the owner only.
go-w deny write permission to group and others.
=rw,+X set the read and write permissions to the usual defaults, but retain any execute permissions that are currently set.
+X make a directory or file searchable/executable by everyone if it is already searchable/executable by anyone.
u=rwx,go=u-w make a file readable/executable by everyone and writable by the owner only.
go= clear all mode bits for group and others.
g=u-w set the group bits equal to the user bits, but clear the group write bit.
The -v option is non-standard and its use in scripts is not recommended.
chflags(1), install(1), setfacl(1), chmod(2), stat(2), umask(2), fts(3), setmode(3), sticky(7), symlink(7), chown(8), mount(8)
The chmod utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible with the exception of the perm symbol ``t'' which is not
included in that standard.
A chmod command appeared in Version 1 AT&T UNIX.
There is no perm option for the naughty bits of a horse.
January 26, 2009 BSD