From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21708 invoked by alias); 19 May 2004 09:23:40 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 21696 invoked from network); 19 May 2004 09:23:37 -0000 Received: from unknown (HELO dessent.net) (66.17.244.20) by sourceware.org with SMTP; 19 May 2004 09:23:37 -0000 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.32) id 1BQNNK-0003W0-4J for cygwin@cygwin.com; Wed, 19 May 2004 09:28:35 +0000 Message-ID: <40AB2792.A4AB6650@dessent.net> Date: Wed, 19 May 2004 09:29:00 -0000 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [OT] RE: Problems listing tasks under cygwin. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com X-SW-Source: 2004-05/txt/msg00671.txt.bz2 Dave Korn wrote: > [ObCygwin] Sysinternals' tools are invaluable for diagnosing cygwin > problems just as much as windoze problems. Trouble with access perms for > your cron daemon service? See what's going on with tokenmon. Trouble with > file access? Filemon will show you what files are involved. Need lofs > functionality? Use HandleEx or ProcExp. And so on! Although I'd still like to know why using ProcExp to list the handles* of any running Cygwin process causes the CPU to peg to 100%, and not come down until cygwin1.dll is unloaded, i.e. kill all running cygwin tasks and services. I've had to train myself when using ProcExp to never accidently click on any Cygwin process, otherwise I have to go through the annoying process of closing all rxvt's and stopping all cygservices in order to get an idle CPU again... I've seen this reported to the list before but it got no replies. It started several notches back in the 1.5 series when there were a large number of changes to the signal handling code, IIRC. [*] It could be listing DLLs that causes it, but I don't want to find out at the moment. Brian -- 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/