Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <20040310085218.31090.qmail@web60305.mail.yahoo.com>
Date: Wed, 10 Mar 2004 00:52:18 -0800 (PST)
From: Patrick Samson <p_samson AT yahoo DOT com>
Subject: Re: select() hangs sometimes, for TCP connections
To: cygwin AT cygwin DOT com
In-Reply-To: <20040226101953.54870.qmail@web60305.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Sorry, I was wrong. Tcl-DP was not the primary
cause.
The story goes on at:
"Backend doesn't catch the next command, after
SIGUSR2"
http://cygwin.com/ml/cygwin/2004-03/msg00418.html

This time with a simpler context:
only pgtclsh and Postgresql.

--- Patrick Samson wrote:
> I finally found the culprit.
> It seems to be a Tcl extension which was badly
> built.
> 
> --- 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.

Correction: this side didn't catch the command, so
will never answer to it.


__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com

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