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
- Re: SIGTERM does not stop backend postgres pro... Jason Tishler
- Re: SIGTERM does not stop backend postgres... Christopher Faylor
- Re: [CYGWIN] Re: SIGTERM does not stop... Hiroshi Inoue
- Re: [CYGWIN] Re: SIGTERM does not... Christopher Faylor
- Re: [CYGWIN] Re: SIGTERM does... Randall R Schulz
- Re: [CYGWIN] Re: SIGTERM does... Christopher Faylor
- RE: SIGTERM does not stop backend postgres processes im... Parker, Ron
- Re: SIGTERM does not stop backend postgres process... Fred Yankowski
- Re: SIGTERM does not stop backend postgres pro... Jason Tishler
- Re: SIGTERM does not stop backend postgres process... Fred Yankowski
- Re: SIGTERM does not stop backend postgres pro... Christopher Faylor
- Re: SIGTERM does not stop backend postgres... Olivier Fambon
- Re: SIGTERM does not stop backend post... Christopher Faylor
- Re: SIGTERM does not stop backend postgres... Fred Yankowski
- Re: SIGTERM does not stop backend post... Christopher Faylor
- Re: SIGTERM does not stop backend... Fred Yankowski
- Re: SIGTERM does not stop bac... Christopher Faylor
- Re: SIGTERM does not stop bac... Tim Baker
- Re: SIGTERM does not stop backend... Robert Collins
- Re: SIGTERM does not stop bac... Corinna Vinschen
- Re: SIGTERM does not stop bac... Jason Tishler