Remove the note about getting stuck when writing to an exited reader, as it was fixed in #189.

This commit is contained in:
Andrew Wood
2026-05-01 19:09:20 +01:00
parent 7a276040ad
commit 096b655bb8
2 changed files with 0 additions and 13 deletions
-7
View File
@@ -877,13 +877,6 @@ a file, that file may look like it has stopped growing if inspected with
reports progress.
This is because of the way sparse output is achieved, and the file will be
the correct size when the transfer ends.
.PP
If \fBpv\fR is writing to a pipe, and the command reading that pipe exits,
\fBpv\fR can only discover that has happened when it \fInext\fR receives
some input data to transfer.
Therefore \*(lq\fBecho\~|\~pv\~|\~sleep\~1\fR\*(rq will wait forever, but
\*(lq\fB{\~echo;\~sleep\~3;\~echo;\~}\~|\~pv\~|\~sleep\~1\fR\*(rq will end
after 3 seconds when \fBpv\fR tries to transfer the second line of input.
.\"
.SH REPORTING BUGS
Please report bugs or feature requests via the issue tracker linked from the
-6
View File
@@ -831,12 +831,6 @@ that file may look like it has stopped growing if inspected with
reports progress. This is because of the way sparse output is achieved,
and the file will be the correct size when the transfer ends.
If **pv** is writing to a pipe, and the command reading that pipe exits,
**pv** can only discover that has happened when it *next* receives some
input data to transfer. Therefore "**echo \| pv \| sleep 1**" will wait
forever, but "**{ echo; sleep 3; echo; } \| pv \| sleep 1**" will end
after 3 seconds when **pv** tries to transfer the second line of input.
# REPORTING BUGS
Please report bugs or feature requests via the issue tracker linked from