On Tuesday 12 May 2009 11:15:24 Y Giridhar Appaji Nag wrote: > On 09/05/12 00:42 +0530, Ritesh Raj Sarraf said ... > > > File size: 142194688 bytes > > Opening output file debian-501-amd64-netinst.iso > > State file found: 17021032 bytes downloaded, 125173656 to go. > > Starting download > > > > [ 13%] [......0 1 2 3 ] [ 95.9KB/s] > > [20:57]^C > > > > Downloaded 1602.1 kilobytes in 17 seconds. (94.20 KB/s) > > > > As you can see above, it does divide it into 4 chunks. But the other > > chunks (or sessions) never start. Or maybe the progress bar is > > misleading and doesn't update properly. > > In this case, 17021032 has already been downloaded and one of the threads > would have been "fast-tracked". The rest of the threads don't display any > "dots" because they are quite lagging wrt that one thread. Also, there > isn't enough "dot resolution" to be able to show the progress they are > making. > Yes. That happened because I wanted to run it in verbose mode before filing the bug. The other threads are not active.
As per axel's documentation,
--alternate, -a
This will show an alternate progress indicator. A bar displays
the progress and status of the different threads, along with
current speed and an estimate for the remaining download time.
I'm using -a but the other threads show no progress.
Actually, they do show progress. But only when the 1st one completes, the 2nd
one starts.
> You could verify that the other threads are making progress by monitoring
> network traffic (using wireshark).
>
I doubt that is the case, but even if it is, the progress bar report is
incorrect.
Ritesh
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
