Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Thu, 25 Jul 2002 21:54:01 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Signals and the such-like Message-ID: <20020726015401.GA11868@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <00af01c2341b$b6138890$6132bc3e AT BABEL> <20020725205402 DOT GC6611 AT redhat DOT com> <001101c23426$55177f00$6132bc3e AT BABEL> <20020725221356 DOT GB8349 AT redhat DOT com> <007101c2342b$ca598e20$6132bc3e AT BABEL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <007101c2342b$ca598e20$6132bc3e@BABEL> User-Agent: Mutt/1.3.23.1i On Thu, Jul 25, 2002 at 11:37:00PM +0100, Conrad Scott wrote: >The best solution so far (from where I'm standing) seems to be a >global "exiting" flag. Is that too unreasonable? I was about to reluctantly say ok and make the "exit_state" variable in do_exit a global but then I started to wonder if this isn't a problem with every call to close_all_files. There are a couple of them outside of the call to do_exit. One is in spawn_guts and one is on vfork. I don't think either of those should hang either, should they? cgf