News for hackers. Stuff that matters.
Re:Pipe Viewer by mibbitier on Thursday May 24, 2012 @04:04PM (#4020277)
How does it know the progress / ETA?

I was under the assumption that pipes do not know how much total data is on its way?

Re:Pipe Viewer by aidenn0 on Thursday May 24, 2012 @04:05PM (#4020287)
If you give it a file, or specify the amount on the commandline it knows, otherwise it doesn't
Re:Pipe Viewer by mbreese on Thursday May 24, 2012 @04:14PM (#4020334)
Right. I usually use pv in place of 'cat' at the start of a long set of piped commands. Anywhere you could use 'cat' you can use pv. If I'm not mistaken, I think you can also use multiple 'pv' commands at a time too.
Re:Pipe Viewer by pronoiac on Thursday May 24, 2012 @05:28PM (#4020663)
> If I'm not mistaken, I think you can also use multiple 'pv' commands at a time too.

I use multiple pv instances to track compression/decompression rates, and overall progress, for tarballs. Using the "-c" code for console codes keeps the instances from stomping over each other's output.

Re:Pipe Viewer by lloeki on Thursday May 24, 2012 @05:45PM (#4020740)
This is indeed visible in the example, only source has progress while bzcat and gzip only have flow.
Re:Pipe Viewer by bsg75 on Thursday May 24, 2012 @04:08PM (#4020304)
You have to supply it the stream sizes if you want completion percentages, otherwise it displays rates only.

Example: https://gist.github.com/2783910