This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: SIGTERM does not stop backend postgres processes immediately
- To: cygwin at cygwin dot com
- Subject: RE: SIGTERM does not stop backend postgres processes immediately
- From: "Parker, Ron" <rdparker at butlermfg dot com>
- Date: Wed, 9 May 2001 16:48:28 -0500
> 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