summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJim Meyering <meyering@redhat.com>2009-12-30 14:23:45 +0100
committerJim Meyering <meyering@redhat.com>2009-12-31 09:42:52 +0100
commitf428e548e52d76a5ed729a2cba9a05f93dad40d9 (patch)
tree51ca71ed06a731c97a4cbd593c9e195a008bf9b7 /doc
parent7e0c2b9a59a610454875340e315d93448fffdb38 (diff)
downloadcoreutils-f428e548e52d76a5ed729a2cba9a05f93dad40d9.tar.xz
doc: update tail's documentation to allow for new -F semantics
* src/tail.c (usage): Reword tail -F description, so that it no longer mentions details specific to the non-inotify implementation. Also, join diagnostic strings (while staying under the 509-byte limit) to ease formatting of translations. The latter was prompted by a report from Stéphane Raimbault. * doc/coreutils.texi (tail invocation): Update description here, too.
Diffstat (limited to 'doc')
-rw-r--r--doc/coreutils.texi6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index e097c257d..5e43b1705 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -2770,8 +2770,10 @@ If you'd like to continue to track the end of a growing file even after
it has been unlinked, use @option{--follow=descriptor}. This is the default
behavior, but it is not useful if you're tracking a log file that may be
rotated (removed or renamed, then reopened). In that case, use
-@option{--follow=name} to track the named file by reopening it periodically
-to see if it has been removed and recreated by some other program.
+@option{--follow=name} to track the named file, perhaps by reopening it
+periodically to see if it has been removed and recreated by some other program.
+Note that the inotify-based implementation handles this case without
+the need for any periodic reopening.
No matter which method you use, if the tracked file is determined to have
shrunk, @command{tail} prints a message saying the file has been truncated