I did some stress testing of lftp over the weekend (read "I got pissed off at someone and did a pget -n 100 at their site") but it failed; corrupt download. It nagged at me a bit until I remebered a recent lftp bug, where it would sometimes not do the Microsoft RETR... The file downloaded had pieces within the file replaced by the start of the file so it's somewhat similar but the server does understand RETR. This only happens when the server is severly overloaded (:-)) so it could be at that end: BUT I was wondering if there's a window between when you reset the 'next get needs a RETR flag' and restore it back to 'RETR from x' say between the various command you send to the server for setting up the download (the server was in sync mode). If so it would cause just the problem I'm seeing. A somewhat saner -n20 got the file successfully at about half the speed. (12-14k/s as opposed to 25k/s) PS: I love my new cable modem :-) PPS: For today :) :) -- Rob. (Robert de Bath <http://poboxes.com/rdebath>) <rdebath @ poboxes.com> <http://www.cix.co.uk/~mayday>
