Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<001201c0d9a6$5327f520$048a42d8@hpcustomer>
From:	"Tim Baker" <dbaker AT direct DOT ca>
To:	<cygwin AT cygwin DOT com>
References:	<E94FF01DFF6CD31186F4080009DC361502086B8D AT nttwr2 DOT tower DOT bldgs DOT butlermfg DOT org> <20010510112639 DOT A26981 AT enteract DOT com> <20010510123102 DOT B15024 AT redhat DOT com> <20010510123628 DOT A48047 AT enteract DOT com> <20010510140721 DOT F12136 AT redhat DOT com> <20010510155340 DOT A25542 AT enteract DOT com> <20010510175304 DOT A19397 AT redhat DOT com>
Subject:	Re: SIGTERM does not stop backend postgres processes immediately
Date:	Thu, 10 May 2001 16:09:53 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200

From: "Christopher Faylor" <cgf AT redhat DOT com>
> >It is hard to see how Cygwin could emulate this in the general case if
> >closing the socket is the only way to unblock recv(win32).  But what's
> >the harm in allowing signals to be handled while in recv(cygwin) even
> >if recv(win32) remains blocked?
> 
> Wow.  There is really a communication breakdown here.  I keep telling
> you that it is not possible to do what you want and you keep acting like
> I'm making policy decisions which, if only I would relent, would solve
> your problems.


He's not "receiving" your meaning.

Me bad.
-- Tim Baker


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -