Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 19 Oct 2003 22:34:28 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: long timeouts on shutdown/log off Message-ID: <20031020023428.GB7554@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20031017153138.GB10560@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Mon, Oct 20, 2003 at 10:53:54AM +0900, Dylan Cuthbert wrote: >Stranger and stranger. > >As there are only 3 in the task list it means that quite a few of the >cron jobs are finishing ok. (I run it every hour) > >But more importantly, why can't winxp kill those tasks properly when I >log off or shutdown? And why has it only started happening in this >latest version of cygwin? I'm glad to see that cygwin is so powerful that it can create unkillable processes. It warms my heart to see that it is gaining in strength and ability. Soon, you won't be able to turn off your machine at all if cygwin is running on it. At that point, cygwin's true insidious purpose will finally be revealed. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/