OK, thank you. Just for your information: We’re using a managed file transfer (MFT) product called Ayway Synchrony Gateway as a multi-protocol service (supports FTP, FTPS, SFTP, HTTPS, and so on). And this solution checks for complete transfers, which means it checks the data flow, if a transfer is correct or not. And if it’s not correct we will get an interrupted transfer. Most of our transfers between Synchrony Gateway <-> lftp works fine, but every now and then we’ll get failed transfers. So this bug is quite important for us, but I wonder why most of the transfers are working fine, if this bug was already in lftp for years. Any idea?
From: Alexander Lukyanov [mailto:lavv...@gmail.com] Sent: Tuesday, October 21, 2014 1:03 PM To: Mütze, Tilo, NMD-C4.2 Subject: Re: [lftp] Question regarding fix in 4.6.0 I mean: it is not fixed in 4.5.6. 21.10.2014 15:01 пользователь "Alexander Lukyanov" <lavv...@gmail.com<mailto:lavv...@gmail.com>> написал: No, it isn't. I have decided that the change is too significant to include in a maintenance release. Use 4.6. And I don't consider it a serious bug - it was there for years and nobody complained. 21.10.2014 14:47 пользователь <tilo.mue...@bertelsmann.de<mailto:tilo.mue...@bertelsmann.de>> написал: Hi Alexander, we’ve seen that in 4.6.0 a bug “ftp: wait for QUIT reply before closing control socket.” was fixed. Can you please tell us, if this fixed bug is present in release 4.5.6 ? Thanks and regards, Tilo _______________________________________________ lftp mailing list lftp@uniyar.ac.ru<mailto:lftp@uniyar.ac.ru> http://univ.uniyar.ac.ru/mailman/listinfo/lftp
_______________________________________________ lftp mailing list lftp@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp
