CC-tea/coreutils
1
0
Fork 0
mirror of git://git.sv.gnu.org/coreutils.git synced 2026-04-18 01:40:06 +02:00
Code Issues Projects Releases Wiki Activity

* man/chmod.x: Correct the description of the sticky bit. Reported

Browse Source 
by Chris Moore via Ian Jackson in <http://bugs.debian.org/376745>.
This commit is contained in:
Jim Meyering
2006-07-05 10:03:55 +00:00
parent 36a288e41a
commit 2a7f886e47
2 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
ChangeLog
View File

@@ -1,5 +1,8 @@
2006-07-05 Jim Meyering <jim@meyering.net>
* man/chmod.x: Correct the description of the sticky bit. Reported
by Chris Moore via Ian Jackson in <http://bugs.debian.org/376745>.
* src/copy.c (copy_internal): Don't work around old NFS clients like
SunOS-4.1.4 and Irix 5.3 that set errno to values like EIO and
ENOTEMPTY upon failed rename. Otherwise, we risk misinterpreting

10
man/chmod.x
View File

@@ -61,11 +61,11 @@ systems, and the Linux kernel ignores the sticky bit on files. Other
kernels may use the sticky bit on files for system-defined purposes.
On some systems, only the superuser can set the sticky bit on files.
.SH STICKY DIRECTORIES
When the sticky bit is set on a directory, files in that directory may
be unlinked or renamed only by root or their owner. Without the
sticky bit, anyone able to write to the directory can delete or rename
files. The sticky bit is commonly found on directories, such as /tmp,
that are world-writable.
When the sticky bit is set on a directory, a file in that directory may
be unlinked or renamed only by the directory owner, the file owner, or root.
Without the sticky bit, anyone able to write to the
directory can delete or rename files. The sticky bit is commonly found
on directories, such as /tmp, that are world-writable.
.SH OPTIONS
[SEE ALSO]
chmod(2)