Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3AFF4B61.39A0B754@tpf.co.jp>
Date: Mon, 14 May 2001 12:05:05 +0900
From: Hiroshi Inoue <Inoue AT tpf DOT co DOT jp>
X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U)
X-Accept-Language: ja
MIME-Version: 1.0
To: Fred Yankowski <fred AT ontosys DOT com>, pgsql-cygwin AT postgresql DOT org
CC: cygwin AT cygwin DOT com, Christopher Faylor <cgf AT redhat DOT com>
Subject: Re: [CYGWIN] Re: SIGTERM does not stop backend postgres processes 
 immediately
References: <20010509094031 DOT A87424 AT enteract DOT com> <20010509142629 DOT J355 AT dothill DOT com> <20010509164926 DOT C3169 AT redhat DOT 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