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:	<E94FF01DFF6CD31186F4080009DC361502086B8D@nttwr2.tower.bldgs.butlermfg.org>
From:	"Parker, Ron" <rdparker AT butlermfg DOT com>
To:	cygwin AT cygwin DOT com
Subject:	RE: SIGTERM does not stop backend postgres processes immediately
Date:	Wed, 9 May 2001 16:48:28 -0500
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)

> Unfortunately, blocking recv() calls are not interruptible on Windows.
> I'm not aware of any mechanism for allowing this.

Under windows two things will interrupt a blocking recv() call.  The first
is to call closesocket() from another thread.  The second is
WSACancelBlockingCall() which no longer exists in Winsock 2, but that is not
a huge problem because cygwin is using Winsock 1.x.

One note, WSACancelBlockingCall() was just a way of getting around the
Winsock 1.1 rule that you couldn't call closesocket() when a blocking call
was pending.  So, closesocket() may have the same effect.

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

- Raw text -