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
On Thu, May 10, 2001 at 12:31:02PM -0400, Christopher Faylor wrote:
> Remember this?
> >Unfortunately, blocking recv() calls are not interruptible on Windows.
> >I'm not aware of any mechanism for allowing this.
Some research led me to believe that closesocket() could unblock a
Win32 recv() call.
> What do you think a signal handler does? It would need to interrupt
> a blocking recv() to work, wouldn't it?
Are you saying that a blocking recv() _must_ never be interrupted,
even if a mechanism exists that would make that possible? If so,
what is the basis for that decision? The recv() specified by the Open
Group [1] seems to allow for an EINTR error case.
[1] http://www.opengroup.org/onlinepubs/7908799/xns/recv.html
--
Fred Yankowski fred@OntoSys.com tel: +1.630.879.1312
Principal Consultant www.OntoSys.com fax: +1.630.879.1370
OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple