On Tue, 23 Sep 2014 01:49:57 -0400 (EDT), Alexander V. Lukyanov wrote: > On Mon, Sep 22, 2014 at 10:02:29PM -0400, Stephen Powell wrote: >> I tried setting both of these server options to yes and tried my "get" with >> lftp again. The last few lines of output in the debug file are now as >> follows: >> >> ---- Got EOF on data connection >> ---- Closing data socket >> <--- 426 Failure writing network stream. >> ---- received all data but no EOF > > Please test this change.
Yes, the patch worked, for this specific test case. But I am having a problem connecting to a different server which does not support TLS. In this case, I'm using lftp interactively instead of via a script. After issuing the close command, I receive the "221 Goodbye." response from the server, and an lftp command prompt. But I can't type anything at the prompt. I type "exit" on the keyboard, but it is not echoed on the screen. The whole program appears to be hung. Eventually, after several minutes, I get a "closing idle connection" message and the exit command shows up on the screen, followed by program termination. I rather doubt that this last patch is responsible. I think it's something in how the close command is processed. It has to work in both TLS and non-TLS environments. It currently seems to have a problem in non-TLS environments. -- .''`. Stephen Powell <zlinux...@wowway.com> : :' : `. `'` `- _______________________________________________ lftp mailing list lftp@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp
