Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 06 May 2003 07:20:36 -0400 From: Jason Tishler Subject: Re: vsftpd corruption problem (Re: proftpd (and vsftpd too)) In-reply-to: To: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20030506112036.GB1280@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <20030505175833 DOT GI556 AT tishler DOT net> On Mon, May 05, 2003 at 10:44:44PM +0200, Hannu E K Nevalainen mail) wrote: > > Any ideas on how to debug this further will be greatly appreciate. > > $ echo $(( $(( 150 * 1024 )) / 64 )) > 2400 > > Wild guesses: > Does "2400" appear as a constant anywhere near transfer buffer counts > or some such? > C/C++ "%" operator in use near buffers? I don't about either of the above, but the corruption does not appear at the same place every time. So, I think that the problem is a race or timeout -- not something as simple as an overflow. I forgot to mention the following data points in my previous post: 1. vsftpd thinks that it transferred the correct number of bytes as indicated by its log file. 2. proftpd does not exhibit this problem Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/