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 To: cygwin@cygwin.com From: Andrew DeFaria Subject: Re: rm problem: Directory not empty Date: Tue, 13 Sep 2005 00:02:50 -0700 Lines: 24 Message-ID: References: <20050912182948.1005.qmail@web31501.mail.mud.yahoo.com> <6.2.1.2.0.20050912150248.02aabb48@pop.prospeed.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.4 (Windows/20050908) In-Reply-To: <6.2.1.2.0.20050912150248.02aabb48@pop.prospeed.net> X-IsSubscribed: yes Larry Hall wrote: > At 02:29 PM 9/12/2005, you wrote: >> I've also seen badly behaving windows programs, which refuse to "let >> go" of a directory once they have used a file in it, until the >> program is explicitly closed. This is most annoying, as you have to >> keep closing program windows until suddenly you guess right, the >> directory is freed, and can be deleted. > 'handle.exe' from is useful in determining the > right app to close in this case. And Process Explorer, also from sysinternals, allows one to not only find the process but to close the open handle while leaving the process running! Process explorer is a full featured replacement for Task Manager that also allows you to kill processes/services that Task Manager doesn't as well as to change priorities of some of those processes that again, Task Manager doesn't. There are some things I do not like about Process Explorer however. 1) Cygwin processes are shown as taking like 4 00 meg of Virtual memory. 2) Lack of a decent Networking graph, 3) Some times Process Explorer and Cygwin trip each other up so that lsass starts consuming all of your CPU. But that aside I still find Process Explorer invaluable. -- All generalizations are false -- 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/