Netgain specifics are closed source and proprietrary, however the BST protocol is
open.
Bug in BST/TCP/NetGain, no matter which it is, the rollback option [when used]
appears to fix the problem quite nicely.
Alexander V. Lukyanov wrote:
On Tue, Apr 09, 2002 at 02:55:25PM +0200, Hrvoje Niksic
If anyone creates a patch for rollback, I'll be your first tester ;)
Justin Piszcz wrote:
I was curious if lftp or wget will ever support a rollback feature and
somehow verify the bytes are correct somehow where the file has been
resumed.
Why? This is stated below:
LFTP VS WGET
For X is great, unless you want to run your downloads in
console :).
[war@p300 x]$ /usr/bin/time md5sum -c file.iso.md5
file.iso: OK
22.56user 5.62system 0:36.38elapsed 77%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (113major+13minor)pagefaults 0swaps
[war@p300 x]$
Justin Piszcz
: Connection timed out; Data transfer
aborted.
Retrying.
This causes corruption in the file.
I need to try a client which supports rollback I guess.
Alexander V. Lukyanov wrote:
On Mon, Apr 01, 2002 at 06:43:49AM -0500, Justin Piszcz wrote:
PROBLEM: With lftp, many of my downloads get
. Lukyanov wrote:
On Tue, Apr 02, 2002 at 09:27:36AM -0500, Justin Piszcz wrote:
My question is: would a 5-10KB rollback fix this problem?
AFAIK, rollback is only needed to workaround broken http proxies, which
output error message after valid data if a transfer error happens.
--
Alexander.
I have tried with over 100s of ftp servers around the world.
The character is a different value.
Alexander V. Lukyanov wrote:
On Mon, Apr 01, 2002 at 06:43:49AM -0500, Justin Piszcz wrote:
PROBLEM: With lftp, many of my downloads get corrupted.
This is because the connection
