hey aysiu. this is where you get creative.
Originally Posted by aysiu
at the very least, i'd like to get confirmation that it runs through without any problems. (edit: ah, i see you've already done that. cool ).
for extra test scenarios, this is what i did:
# i edited the keyserver list to include some nonexistent servers, to give it a chance to fail and move on to another keyserver.
# i made the verification run without a tar.gz present, which of course resulted in verification failure, and gave it a chance to do its thing
# i did not test the timeout thing, but conceivably what you could do is pull the network plug out for 60 secs in the middle of the download, and see if it attempts to restart. but it really does not require extra testing, since it's just a built-in feature of wget - it's not something i rigged up with the script.
about the 60sec timetout: it is not the total download time, but the time during which you receive no data. so, if your download is "stalled" and you receive no data for 60 seconds, it kills that connection, and starts another, continuing from where it left off. so even if you are on dialup, if you receive no data for 60 seconds, that's a pretty good indication that the download has stalled out.
(from the wget manpage:
Set the read (and write) timeout to seconds seconds. The ‘‘time’’ of this timeout
refers idle time: if, at any point in the download, no data is received for more
than the specified number of seconds, reading fails and the download is restarted.
This option does not directly affect the duration of the entire download.