bit will be turned off,
but this will not cause an error to be returned.
-As a security measure, depending on the filesystem,
+As a security measure, depending on the file system,
the set-user-ID and set-group-ID execution bits
may be turned off if a file is written.
(On Linux this occurs if the writing process does not have the
.B CAP_FSETID
capability.)
-On some filesystems, only the superuser can set the sticky bit,
+On some file systems, only the superuser can set the sticky bit,
which may have a special meaning.
For the sticky bit, and for set-user-ID and set-group-ID bits on
directories, see
.BR stat (2).
-On NFS filesystems, restricting the permissions will immediately influence
+On NFS file systems, restricting the permissions will immediately influence
already open files, because the access control is done on the server, but
open files are maintained by the client.
Widening the permissions may be
.I errno
is set appropriately.
.SH ERRORS
-Depending on the filesystem, other errors can be returned.
+Depending on the file system, other errors can be returned.
The more general errors for
.BR chmod ()
are listed below:
capability).
.TP
.B EROFS
-The named file resides on a read-only filesystem.
+The named file resides on a read-only file system.
.PP
The general errors for
.BR fchmod ()