Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 13 Feb 2004 09:32:40 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: select() hangs sometimes, for TCP connections Message-ID: <20040213143240.GC4672@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <20040213122720.17765.qmail@web60301.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040213122720.17765.qmail@web60301.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com On Fri, Feb 13, 2004 at 04:27:19AM -0800, Patrick Samson wrote: >Problem: sometimes select() doesn't return. > >Context: I run a DB replication scenario, with cron, everything 5 mn. >There is no change in the DB, so the scenario is always the same. Most >of the time, it works. But eventually, after some time (may be some >minutes or hours), a process A keeps waiting forever in select() for a >response on a TCP socket. With gdb I can see that the other end B >returned in its ReadCommand() function, meaning it has send its >response and waits for a new command, so this side should be OK. I suspect that this is basically a winsock socket reuse bug that has been around for a long time. Corinna, does this ring a bell? cgf -- 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/