Hey, thanks for your response. But I do think that there must have been changed something in lftp, as older version 3.2.1 works fine with the same server... Furthermore, as I described, the problem does only occure when transfer time is longer than net:timeout value, so there seems to be any interconnection between them :-( In fact, the lftp client doesn't even wait for a confirmation, moreover, it catches a timeout immediately, so there is no chance for the server to confirm successful transfer.
2006-11-01 13:04:23 copy: waiting for put confirmation 2006-11-01 13:04:23 FileCopy(139ea0) enters state CONFIRM_WAIT 2006-11-01 13:04:23 ---- Closing data socket 2006-11-01 13:04:23 **** Timeout - reconnecting 2006-11-01 13:04:23 ---- Closing control socket Best regards Stefan. On 12/4/06, Alexander V. Lukyanov <[EMAIL PROTECTED]> wrote:
On Mon, Dec 04, 2006 at 10:25:27AM +0100, [EMAIL PROTECTED]: > is there anybody who can tell me something about this issue? Is it a bug or > a feature? It is certainly a bug, but probably not in lftp. lftp waits for server reply which confirms successful transfer, but does not receive it for some reason. -- Alexander.
