summaryrefslogtreecommitdiff
path: root/man/chmod.x
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2006-07-05 10:03:55 +0000
committerJim Meyering <jim@meyering.net>2006-07-05 10:03:55 +0000
commit2a7f886e47f95cee00ebff12e58d0ad7595a9cca (patch)
treef3b6c950de6c72e4ec7defa4e47b19b4a5ba4725 /man/chmod.x
parent36a288e41a6534c816090dce1a6ed139a60e87b7 (diff)
downloadcoreutils-2a7f886e47f95cee00ebff12e58d0ad7595a9cca.tar.xz
* man/chmod.x: Correct the description of the sticky bit. Reported
by Chris Moore via Ian Jackson in <http://bugs.debian.org/376745>.
Diffstat (limited to 'man/chmod.x')
-rw-r--r--man/chmod.x10
1 files changed, 5 insertions, 5 deletions
diff --git a/man/chmod.x b/man/chmod.x
index 497206667..ab5c88492 100644
--- a/man/chmod.x
+++ b/man/chmod.x
@@ -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)