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 Message-ID: <3AFF4B61.39A0B754@tpf.co.jp> Date: Mon, 14 May 2001 12:05:05 +0900 From: Hiroshi Inoue X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: Fred Yankowski , pgsql-cygwin@postgresql.org CC: cygwin@cygwin.com, Christopher Faylor Subject: Re: [CYGWIN] Re: SIGTERM does not stop backend postgres processes immediately References: <20010509094031.A87424@enteract.com> <20010509142629.J355@dothill.com> <20010509164926.C3169@redhat.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit 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. regards, Hiroshi Inoue -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple