1 |
On Mon, 2006-03-27 at 22:33 +0200, Simon Kellett wrote: |
2 |
> Iain Buchanan <iaindb@××××××××××××.au> writes: |
3 |
> |
4 |
> > So the question is: why does wget try to download it from the |
5 |
> > beginning? wget shouldn't do this even if the server can't resume, |
6 |
> > wget should just die. |
7 |
> |
8 |
> man wget :-) |
9 |
|
10 |
ok: |
11 |
|
12 |
Beginning with Wget 1.7, if you use -c on a non-empty file, and it |
13 |
turns out that the server does not support continued downloading, |
14 |
Wget will refuse to start the download from scratch, which would |
15 |
effectively ruin existing contents. If you really want the down- |
16 |
load to start from scratch, remove the file |
17 |
|
18 |
and yet the file did start from scratch... |
19 |
|
20 |
> "Note that -c only works with FTP servers and with HTTP servers that |
21 |
> support the "Range" header." |
22 |
> |
23 |
> I am guessing his does not ! |
24 |
|
25 |
actually, it does, as on another file: |
26 |
|
27 |
$ wget -c |
28 |
"http://68.106.74.139/mp3/Mike_Baas/4/mp3/Mike_Baas_-_4_-_03_-_Wave.mp3" |
29 |
--09:56:35-- |
30 |
http://68.106.74.139/mp3/Mike_Baas/4/mp3/Mike_Baas_-_4_-_03_-_Wave.mp3 |
31 |
=> `Mike_Baas_-_4_-_03_-_Wave.mp3' |
32 |
Connecting to 68.106.74.139:80... connected. |
33 |
HTTP request sent, awaiting response... 206 Partial Content |
34 |
Length: 13,985,672 (13M), 234,426 (229K) remaining [audio/mpeg] |
35 |
|
36 |
100%[++++++++++++++++++++++++++++++++++++>] 13,985,672 8.97K/s |
37 |
ETA 00:00 |
38 |
|
39 |
09:56:57 (11.18 KB/s) - `Mike_Baas_-_4_-_03_-_Wave.mp3' saved |
40 |
[13985672/13985672] |
41 |
|
42 |
|
43 |
But even if it didn't this still wouldn't explain why the download is |
44 |
deleted, and then downloaded again. -c shouldn't do that. |
45 |
|
46 |
thanks, |
47 |
-- |
48 |
Iain Buchanan <iaindb at netspace dot net dot au> |
49 |
|
50 |
If you want to know what god thinks of money, just look at the people he gave |
51 |
it to. |
52 |
-- Dorthy Parker |
53 |
|
54 |
-- |
55 |
gentoo-user@g.o mailing list |