1. It would help to know the wget version ("wget -V").
2. It might help to see some output when you add "-d" to the wget
command line. (One existing file should be enough.) It's not
immediately clear whose fault the 416 error is. It might also help to
know which Web server is running on the server, and how big the file is
which you're trying to re-fetch.
> This was surprising [...]
You're easily surprised.
> wget: realloc: Failed to allocate 536870912 bytes; memory exhausted.
500MB sounds to me like a lot.
> [...] it exhausts the memory on my test box which has 2GB.
A "memory exhausted" complaint here probably refers to virtual
memory, not physical memory.
> [...] I do not want it to check to see if the file is
> newer, if the file is complete, just skip it and go on to the next
> file.
I haven't checked the code, but with "continue=on", I'd expect wget
to check the size and date together, and not download any real data if
the size checks, and the local file date is later. The 416 error
suggests that it's trying to do a partial (byte-range) download, and is
failing because either it's sending a bad byte range, or the server is
misinterpreting a good byte range. Adding "-d" should show what wget
thinks that it's sending. Knowing that and the actual file size might
show a problem.
If the "-d" output looks reasonable, the fault may lie with the
server, and an actual URL may be needed to persue the diagnosis from
there.
The memory allocation failure could be a bug, but finding it could be
difficult.
------------------------------------------------------------------------
Steven M. Schweda [EMAIL PROTECTED]
382 South Warwick Street (+1) 651-699-9818
Saint Paul MN 55105-2547
