wget retry/resume problem

  • wdoe999
  • Born
  • Born
  • wdoe999
  • Posts: 2

Post 3+ Months Ago

Hi - I am having a problem with wget v1.10.2 when I run the command:

wget -t 100 -T 10 -i files.txt

On older versions (eg v1.6), this will keep retrying and will "resume"
the download from where it left off, EVERY time.

On the latest wget version, this will do the retry properly if the
connection times-out in the middle of receiving bytes (read-error),
however, if there is a timeout when receiving the header response from
the server, wget will start all over again and will not resume.

Here is a sample of the error:
-------------------
HTTP request sent, awaiting response... Read error (Connection timed
out) in headers.
------------------

I've looked at all the switches and can't figure out how to make this
work like the older versions. Does anybody have any solutions, or is
this a bug?
  • Anonymous
  • Bot
  • No Avatar
  • Posts: ?
  • Loc: Ozzuland
  • Status: Online

Post 3+ Months Ago

  • Don2007
  • Web Master
  • Web Master
  • Don2007
  • Posts: 4924
  • Loc: NY

Post 3+ Months Ago

A google search showed that you're not the only one with that problem but I didn't see an answer to it.
May I suggest the 'report a bug' section on:
http://www.gnu.org/software/wget/wget.html
  • wdoe999
  • Born
  • Born
  • wdoe999
  • Posts: 2

Post 3+ Months Ago

Hi - I fingered-it-out. I used the -c switch.

The instructions say that the -c switch is used to "continue" a
download from a previous invocation of wget. The problem is that they
explicitly say that the -c option does not do anything for the
"current" invocation of wget. That is why I never tried it to begin-
with. After I thought about it for a while, I started to think that
wget is "essentially" starting a new download when it gets a fatal
error, and perhaps the instructions could be wrong. Indeed this is
true and the -c option does have affect in the current invocation.

I wonder if you can report a bug in the instructions?
  • Don2007
  • Web Master
  • Web Master
  • Don2007
  • Posts: 4924
  • Loc: NY

Post 3+ Months Ago

No, incomplete documentation doesn't constitute a bug. However, you could send an email to the current maintainer listed on the gnu site.
mauro@ferrara.linux.it

Post Information

  • Total Posts in this topic: 4 posts
  • Users browsing this forum: No registered users and 75 guests
  • You cannot post new topics in this forum
  • You cannot reply to topics in this forum
  • You cannot edit your posts in this forum
  • You cannot delete your posts in this forum
  • You cannot post attachments in this forum
 
cron
 

© 1998-2014. Ozzu® is a registered trademark of Unmelted, LLC.