"Perry E. Metzger" wrote:

> 
> Hubert Feyrer <hubertf@netbsd.org> writes:
> > Module Name:	src
> > Committed By:	hubertf
> > Date:		Thu Apr 20 23:20:55 UTC 2006
> >
> > Modified Files:
> > 	src/usr.bin/progress: progress.c
> >
> > Log Message:
> > Don't try to determining the size of what's coming when reading from a pipe.
> > Instead of reporting some bogus values, print no progress at all.
> > (It's beyond me why stat(2) on a pipe returns funny values...
> >  see the PR below for some examples!)
> >
> > Fixes PR bin/33207 by myself.
> 
> Actually, there is a sane thing you could do, which would be to
> twiddle something as packets come in and report an absolute count of
> how much had been pushed through. That way, although you don't know
> how long things will take, you can at least tell that something is
> moving.

Isn't this exactly what very old progress(1) did, and new progress(1)
does now, as described in the PR?

Simon.
--
Simon Burge                            <simonb@wasabisystems.com>
NetBSD Support and Service:         http://www.wasabisystems.com/