Hi, doing the following: # /tmp/wget-1.9-beta3/src/wget -r --timeout=5 --tries=1 http://weather.cod.edu/digatmos/syn/ --11:33:16-- http://weather.cod.edu/digatmos/syn/ => `weather.cod.edu/digatmos/syn/index.html' Resolving weather.cod.edu... 192.203.136.228 Connecting to weather.cod.edu[192.203.136.228]:80... failed: Connection timed out. Giving up.
FINISHED --11:33:21-- Downloaded: 0 bytes in 0 files # echo $? 0 If wget aborts because of an timeout (all --*-timeout options), it sets an exit status of 0, which is not what users are expecting, and which makes it very difficult to catch such aborts. Using "--non-verbose" in this example, I get no response at all that something might have failed. An abort has nothing to do with being verbose or not, it should always be notified in some way, IMHO. Further more, wget man and info pages should document the exit status, I could not find any documentation about wget's exit status. In contrast, curl does the right thing (non-zero exit status): # curl -r --connect-timeout 5 http://weather.cod.edu/digatmos/syn/ curl: (7) # echo $? 7 regards Manfred ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
