Re: select() hangs sometimes, for TCP connections

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Feb 13 09:32, Christopher Faylor wrote:
> 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?

Hmm... no, not off top of my head.  Any additional hint?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/