| 1 |
Hi all, |
| 2 |
|
| 3 |
when using wget recently to get some "free" mp3's from Mike Baas' |
| 4 |
website, I had to kill it halfway through to do some other downloading. |
| 5 |
|
| 6 |
When I continued, I used `wget -c ...` but I got "strange" behaviour: |
| 7 |
|
| 8 |
$ wget -c |
| 9 |
"http://68.106.74.139/mp3/Mike_Baas/4/mp3/Mike_Baas_-_4_-_01_-_Why_Can't_I_Slow_The_World_Down.mp3" --10:38:16-- http://68.106.74.139/mp3/Mike_Baas/4/mp3/Mike_Baas_-_4_-_01_-_Why_Can't_I_Slow_The_World_Down.mp3 => `Mike_Baas_-_4_-_01_-_Why_Can't_I_Slow_The_World_Down.mp3' Connecting to 68.106.74.139:80... connected. HTTP request sent, awaiting response... 200 OK Length: 13,870,871 (13M) [audio/mpeg] |
| 10 |
|
| 11 |
50% [=================> ] 13,870,871 3.67M/s |
| 12 |
ETA 00:04 |
| 13 |
|
| 14 |
10:38:19 (3.69 MB/s) - |
| 15 |
`Mike_Baas_-_4_-_01_-_Why_Can't_I_Slow_The_World_Down.mp3' saved |
| 16 |
[13870871/13870871] |
| 17 |
|
| 18 |
As you can see, wget didn't continue, instead it tried to download the |
| 19 |
complete file again. It must also be cached by squid, because I |
| 20 |
certainly don't get 3.67 M/s on our shared 512k line :) |
| 21 |
|
| 22 |
So the question is: why does wget try to download it from the beginning? |
| 23 |
wget shouldn't do this even if the server can't resume, wget should just |
| 24 |
die. |
| 25 |
|
| 26 |
And why also does it not appear to finish, even though the mp3 sounds |
| 27 |
complete? |
| 28 |
|
| 29 |
many thanks, |
| 30 |
-- |
| 31 |
Iain Buchanan <iaindb at netspace dot net dot au> |
| 32 |
|
| 33 |
Loneliness is a terrible price to pay for independence. |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-user@g.o mailing list |
Archives