tail -f file SIGABRT if file size increased 1PB
Open
Nobody has claimed this yet.
U - tail
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
$ truncate -s 1M /tmp/huge
$ gnu9.11/tail -f /tmp/huge|pv>/dev/null
different term $ truncate -s 1PB /tmp/huge
^C.3GiB 0:00:12 [2.17GiB/s]
But with uutils,
$ truncate -s 1M /tmp/huge
$ tail -f /tmp/huge|pv>/dev/null
1.00MiB 0:00:03 [ 293KiB/s]
different term $ truncate -s 1PB /tmp/huge
fish: Process 2052, 'tail' from job 1, 'tail -f /tmp/huge|pv>/dev/null' terminated by signal SIGKILL (Forced quit)
It potentially crashes log monitoring scripts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure by running tail -f on a file and expanding it from 1M to 1PB with truncate. Trace the tail implementation and its file-size growth handling, then verify that monitoring continues without termination after the size increase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100