Herold Heiko [EMAIL PROTECTED] writes:
At the moment I wrote (rather badly) the waitretry patch I thought
at backwards compatibility for existing installations - that is,
somebody with new wget, but existing .wgetrc (no waitretry set) and
existing scripts (no --waitretry set) should hammer
The retry mechanism might be okay for http, but many ftp sites consider
retries within 60 seconds as hammering.
If backward compatibility is the goal, it would seem that this could be
achieved by setting the default waitretry to 0, and leave it there if
there is no other specification.
Philip Chong [EMAIL PROTECTED] writes:
Currently with wget-1.7, the value of waitretry is ignored from both
the user's ~/.wgetrc and SYSTEM_WGETRC. The compatibility hack in
line 697 of src/main.c overwrites any waitretry value specified in
~/.wgetrc with the wait value, and the only way to
Hi:
Currently with wget-1.7, the value of waitretry is ignored from both
the user's ~/.wgetrc and SYSTEM_WGETRC. The compatibility hack in line
697 of src/main.c overwrites any waitretry value specified in ~/.wgetrc
with the wait value, and the only way to prevent this is to specify
--waitretry
