Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 30 Mar 2004 11:44:30 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Postgres Backend doesn't catch the next command, after SIGUSR2 Message-ID: <20040330094430.GG17229@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040329141651 DOT GZ17229 AT cygbert DOT vinschen DOT de> <20040330090300 DOT 81137 DOT qmail AT web60310 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040330090300.81137.qmail@web60310.mail.yahoo.com> User-Agent: Mutt/1.4.2i On Mar 30 01:03, Patrick Samson wrote: > >From msdn: > "All I/O operations that are canceled will complete > with the error ERROR_OPERATION_ABORTED. All completion > notifications for the I/O operations will occur > normally." Urgh, I mised that. > What's your feeling about: > if (!CancelIo ((HANDLE) socket)) > {...} > else > { > if (WSAGetOverlappedResult (socket, &ovr, &len, > FALSE, flags) && len != 0) > ret = (int) len; > else WSASetLastError (WSAEINTR); Did you try it? Yesterday I changed Cygwin to use asynchronous I/O instead of overlapped I/O so it now can do without CancelIo. However, two people reported hangs which don't occur for me. If if takes too long to track down, I guess I'll revert to overlapped I/O plus your patch. But I would be more happy with a working async I/O solution. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/