SIGTERM does not stop backend postgres processes immediately

[Christopher Faylor]

On Thu, May 10, 2001 at 11:26:39AM -0500, Fred Yankowski wrote:
>To unblock recv() on receipt of a signal -- SIGHUP in particular, for
>this test -- I set up a signal handler that calls close() on the
>socket fd.  It looks to me like this should call
>fhandler_socket::close() on that fd, which then calls closesocket() on
>the underlying Win32/winsock SOCKET, which is purported to unblock
>the Win32 recv() call on that socket.

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

What do you think a signal handler does?  It would need to interrupt
a blocking recv() to work, wouldn't it?

cgf

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