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
Date:	Fri, 27 Apr 2001 12:09:14 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin service doesn't get NT shutdown notification
Message-ID:	<20010427120914.A7541@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20010426113527 DOT A99410 AT enteract DOT com> <3AE8215E DOT 30294 DOT 3E93F1 AT localhost> <20010426181503 DOT C360 AT redhat DOT com> <20010427104723 DOT B63579 AT enteract DOT com>
Mime-Version:	1.0
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

- Raw text -