Hi everybody:
Few days ago I ask a question
After days retrieving,everytime I start wget.Wget
always spend lots of time to check whether these exist
files are retrieved or updated.Even transmission time
are much shorter than checking.
As time goes by,due to the large amount of file
From: Robert Denton
> Can you glean from the code what would cause an exit value 0?
Zero is the success code, which is the default, so anything which
does not set 1 or 2 should leave 0.
> 0: -I have never seen this one -
What do you see when everything goes right? (Or do your jobs always
Steven, thanks for the info! Just from frequent usage of wget (and
not from examining the code) I have come to think of the exit values
like this:
0: -I have never seen this one -
1: communication failures
2: option/syntax related problems
Can you glean from the code what would cause an exit
Hi everybody,
I think there is a bug storing cookies with wget.
See this command line:
"C:\Programme\wget\wget" --user-agent="Opera/8.5 (X11;
U; en)" --no-check-certificate --keep-session-cookies
--save-cookies="cookie.txt" --output-document=-
--debug --output-file="debug.txt"
--post-data="name=
>> [...] An upgrade to the latest revision of 1.10.2 exhibited the
>> problems and a downgrade avoided the problems.
> Do these apparently different variants of wget version 1.10.2 say
>different things in the "wget -V" report?
They both report as:
GNU Wget 1.10.2 (Red Hat modified)
It appears
