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: Fri, 27 Apr 2001 12:09:14 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Cygwin service doesn't get NT shutdown notification Message-ID: <20010427120914.A7541@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010426113527.A99410@enteract.com> <3AE8215E.30294.3E93F1@localhost> <20010426181503.C360@redhat.com> <20010427104723.B63579@enteract.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010427104723.B63579@enteract.com>; from fred@ontosys.com on Fri, Apr 27, 2001 at 10:47:23AM -0500 On Fri, Apr 27, 2001 at 10:47:23AM -0500, Fred Yankowski wrote: >On Thu, Apr 26, 2001 at 06:15:03PM -0400, Christopher Faylor wrote: >> I assume that this problem actually has something to do with the way >> Cygwin handles signals and the way it traps things like "shutdown >> events". > >That's one of my favorite hypotheses as well. > >> Inspection of Cygwin code would probably be pretty enlightening in >> that regard. > >I'm sorry to say that I spent several hours pouring over the source >for the cygwin package and couldn't find enlightenment. I just don't >understand much of the Cygwin architecture. If someone can steer me >in the right direction or give me something to focus on, I will >happily dive back into the code. grep -i "shutdown" *.cc cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple