src/lib/libc/sys/chmod.2, branch release/11.1.0 FreeBSD source tree chmod(2): Document S_ISVTX following SUSv3/SUSv4. 2013-12-01T12:24:57+00:00 Jilles Tjoelker jilles@FreeBSD.org 2013-12-01T12:24:57+00:00 b865f8ef405f90a052c20d458930d11659409e13 S_ISTXT is non-standard. While here, also update fchmodat() standards entry to POSIX.1-2008. 
S_ISTXT is non-standard.

While here, also update fchmodat() standards entry to POSIX.1-2008.
Update sticky(7) cross references. 2011-05-13T16:29:57+00:00 Sergey Kandaurov pluknet@FreeBSD.org 2011-05-13T16:29:57+00:00 e2ea39cbdbfb41e6bd37de5c361a55f33e21a37a PR: docs/124468 X-MFC with: r218998 
PR:		docs/124468
X-MFC with:	r218998
Man pages for the openat(2), fexecve(2) and related syscalls. 2008-04-16T13:03:12+00:00 Konstantin Belousov kib@FreeBSD.org 2008-04-16T13:03:12+00:00 a141af6930ff64262ef4d0fd13f4edf8e266d5fe Reviewed by: ru 
Reviewed by:	ru
When we try to set set-gid bit with chmod(2) on a file, which we own, but our 2007-01-16T15:17:27+00:00 Pawel Jakub Dawidek pjd@FreeBSD.org 2007-01-16T15:17:27+00:00 e9f0620b9faa632e5fb2bc226a93fcd9f724c562 effective group ID (and any of our group) doesn't match the group ID of the file, we get EPERM. This doesn't conform POSIX. POSIX requires that we should return 0, but silently clear the set-gid bit. 
effective group ID (and any of our group) doesn't match the group ID of the
file, we get EPERM.  This doesn't conform POSIX. POSIX requires that we should
return 0, but silently clear the set-gid bit.
Per Regents of the University of Calfornia letter, remove advertising 2007-01-09T00:28:16+00:00 Warner Losh imp@FreeBSD.org 2007-01-09T00:28:16+00:00 c879ae3536e6d92b8d96c8965c5b05fcb9541520 clause. # If I've done so improperly on a file, please let me know. 
clause.

# If I've done so improperly on a file, please let me know.
Much more correct EFTYPE description. 2006-12-13T13:46:01+00:00 Pawel Jakub Dawidek pjd@FreeBSD.org 2006-12-13T13:46:01+00:00 a4319b6585357ce1e34bbeb7a2690dbf204c9090 






Append-only flag also denies chmod(2). Is this correct behaviour?
2006-12-13T13:22:57+00:00

Pawel Jakub Dawidek
pjd@FreeBSD.org

2006-12-13T13:22:57+00:00

3bb2bdaef6b8952c745f256359cc4c195bb7baa4












If the named file has its immutable flag set, chmod(2) returns EPERM.
2006-12-09T22:41:01+00:00

Pawel Jakub Dawidek
pjd@FreeBSD.org

2006-12-09T22:41:01+00:00

54ec563e0d9eb8f59e5c68e4c48d8f13877fc998












Catch up with stat.h a bit:
2004-12-29T20:00:29+00:00

Tom Rhodes
trhodes@FreeBSD.org

2004-12-29T20:00:29+00:00

a51d79c1d379b3855ceaf21a2078456665285a0d

o Sticky bit is actually defined as S_ISTXT not S_ISVTX.
o Sticky bit is wrapped in if __BSD_VISIBLE not _POSIX_SOURCE.





o Sticky bit is actually defined as S_ISTXT not S_ISVTX.
o Sticky bit is wrapped in if __BSD_VISIBLE not _POSIX_SOURCE.







Mechanically kill hard sentence breaks.
2004-07-02T23:52:20+00:00

Ruslan Ermilov
ru@FreeBSD.org

2004-07-02T23:52:20+00:00

1a0a934547909744a6a2fa4cfd5b795ec6394f05