Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 9 May 2001 16:49:26 -0400 From: Christopher Faylor To: cygwin@cygwin.com Cc: Fred Yankowski , pgsql-cygwin@postgresql.org Subject: Re: SIGTERM does not stop backend postgres processes immediately Message-ID: <20010509164926.C3169@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com, Fred Yankowski , pgsql-cygwin@postgresql.org References: <20010509094031.A87424@enteract.com> <20010509142629.J355@dothill.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010509142629.J355@dothill.com>; from Jason.Tishler@dothill.com on Wed, May 09, 2001 at 02:26:29PM -0400 On Wed, May 09, 2001 at 02:26:29PM -0400, Jason Tishler wrote: >> I know from inserting printfs into the backend code that the SIGTERM >> signal handler function is not being called right after the stop >> request. Rather, it is called only after the backend gets some data >> over its input socket connection, from that "\d" in did in pg_ctl in >> this case. It seems that the recv() call deep in the backend code >> does not get interrupted by the SIGTERM. > >IMO, you have found a Cygwin bug. Please report it to the Cygwin list. >Hopefully, Mr. Signal is listening and will jump into action... Unfortunately, blocking recv() calls are not interruptible on Windows. I'm not aware of any mechanism for allowing this. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple