summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2006-01-21 11:16:43 +0000
committerJim Meyering <jim@meyering.net>2006-01-21 11:16:43 +0000
commitaf1885b91f4798514fa28a79d9ea1dd6d1f71a54 (patch)
tree65c0f3afa94149eeca4942aed3ab0701f1a28ea9
parent4393cb56ca9b54c0b8e8ad0c782d8a9a2635b522 (diff)
downloadcoreutils-af1885b91f4798514fa28a79d9ea1dd6d1f71a54.tar.xz
Mention fts-related improvements and bug fixes.
-rw-r--r--NEWS11
1 files changed, 11 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index ed2ff9643..25a2bbcfc 100644
--- a/NEWS
+++ b/NEWS
@@ -7,6 +7,9 @@ GNU coreutils NEWS -*- outline -*-
rm's core is now reentrant: rm --recursive (-r) now processes
hierarchies without changing the working directory at all.
+ fts no longer changes the current working directory, so its clients
+ (chmod, chown, chgrp, du) no longer malfunction under extreme conditions.
+
** Changes in behavior
df now considers "none" and "proc" file systems to be dummies and
@@ -73,6 +76,14 @@ GNU coreutils NEWS -*- outline -*-
** Bug fixes
+ fts-using tools (chmod, chown, chgrp, du) no longer fail due to
+ a double-free bug -- it could be triggered by making a directory
+ inaccessible while e.g., du is traversing the hierarchy under it.
+
+ fts-using tools (chmod, chown, chgrp, du) no longer misinterpret
+ a very long symlink chain as a dangling symlink. Before, such a
+ misinterpretation would cause these tools not to diagnose an ELOOP error.
+
rm (on systems with openat) can no longer exit before processing
all command-line arguments.