Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Authentication-Warning: shell-3.enteract.com: fcy set sender to fred AT ontosys DOT com using -f Date: Thu, 10 May 2001 12:36:28 -0500 From: Fred Yankowski To: cygwin AT cygwin DOT com Subject: Re: SIGTERM does not stop backend postgres processes immediately Message-ID: <20010510123628.A48047@enteract.com> References: <20010510112639 DOT A26981 AT enteract DOT com> <20010510123102 DOT B15024 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010510123102.B15024@redhat.com>; from cgf@redhat.com on Thu, May 10, 2001 at 12:31:02PM -0400 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 AT OntoSys DOT 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