diff options
| author | Jim Meyering <meyering@redhat.com> | 2009-11-15 09:25:29 +0100 |
|---|---|---|
| committer | Jim Meyering <meyering@redhat.com> | 2009-11-16 09:30:43 +0100 |
| commit | 3b997a9bcb05198c880e5d1605a3c96c1d7f9c5d (patch) | |
| tree | 99d9c5b1943e2339986e78e8bfac2c6f506aa424 /NEWS | |
| parent | 00f0cabaecdd490529d05230435671eb89a7b5c5 (diff) | |
| download | coreutils-3b997a9bcb05198c880e5d1605a3c96c1d7f9c5d.tar.xz | |
tail -F can fail to track a file after it's been rotated
Tailing forever and by-name (--follow=name, -F), tail would
sometimes fail to follow a file that had been removed via rename.
If you can't apply this patch and have tail 7.6 or newer, you can
work around the bug via the undocumented --disable-inotify option.
* src/tail.c (tail_forever_inotify): When tailing by name (-F),
do not un-watch a file upon receipt of the IN_MOVE_SELF event.
Reported by Arjan Opmeer in http://bugs.debian.org/548439.
* NEWS (Bug fixes): Mention it.
Also see http://marc.info/?l=coreutils-bug&m=125829031916515
* tests/Makefile.am (TESTS): Add tail-2/inotify-rotate.
* tests/tail-2/inotify-rotate: New test.
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -48,6 +48,11 @@ GNU coreutils NEWS -*- outline -*- were first renamed or unlinked or never modified. [The race was introduced in coreutils-7.5] + tail -F (inotify-enabled) now consistently tails a file that has been + replaced via renaming. That operation provokes either of two sequences + of inotify events. The less common sequence is now handled as well. + [The bug came with the implementation change in coreutils-7.5] + timeout now doesn't exit unless the command it is monitoring does, for any specified signal. [bug introduced in coreutils-7.0]. |