Differences between current version and previous revision of fchmod(2).
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 4 | Last edited on Thursday, October 31, 2002 10:21:28 pm | by JohnMcPherson | |
Older page: | version 3 | Last edited on Thursday, October 31, 2002 10:06:21 pm | by PerryLorier | Revert |
@@ -56,8 +56,8 @@
!!CONFORMING TO
The fchmod(2) call conforms to 4.4BSD and SVr4. SVr4 documents additional [EINTR] and [ENOLINK] error conditions. POSIX requires the fchmod(2) function if at least one of POSIX_MAPPED_FILES and _POSIX_SHARED_MEMORY_OBJECTS is defined, and documents additional [ENOSYS] and [EINVAL] error conditions, but does not document [EIO].
-POSIX and X/OPEN do not document the sticky bit.
+[
POSIX]
and X/OPEN do not document the sticky bit.
!!SEE ALSO
open(2), chown(2), execve(2), stat(2)