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: Sun, 13 May 2001 23:14:32 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [CYGWIN] Re: SIGTERM does not stop backend postgres processes immediately Message-ID: <20010513231432.A5059@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010509094031.A87424@enteract.com> <20010509142629.J355@dothill.com> <20010509164926.C3169@redhat.com> <3AFF4B61.39A0B754@tpf.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3AFF4B61.39A0B754@tpf.co.jp>; from Inoue@tpf.co.jp on Mon, May 14, 2001 at 12:05:05PM +0900 On Mon, May 14, 2001 at 12:05:05PM +0900, Hiroshi Inoue wrote: >Christopher Faylor wrote: >>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. > >How about inserting a select() call before the recv() ? Cygwin's >select() is interruptible AFAIK. That would be the "workaround" that I kept mentioning previously. It relies on polling and that is a something I'd rather avoid, if possible. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple