Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <41827FB9.1060003@x-ray.at> Date: Fri, 29 Oct 2004 19:36:57 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a3) Gecko/20040817 MIME-Version: 1.0 To: Superbiskit AT cox DOT net CC: Cygwin General Discussion Subject: Re: BUG: Cygwin implementation of Debian package tools References: <418278CB DOT 6080204 AT cox DOT net> In-Reply-To: <418278CB.6080204@cox.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes David A. Cobb schrieb: > Getting tired of loading disks, I structured a local mirror of the > Debian directory structure and tried running Cygwin > dpkg-scanpackages. I expected it to take a while, so I wasn't > surprised - I just went and make some more coffee. But after 20 > minutes I suspected something was wrong and fired up ProcessExplorer. > Under my console bash I discovered: > +perl (OK, dpkg-scanpackeages is a big perl script I guess) > ++dpkg-deb > ++rm.exe <==== getting 98% of the CPU time and not making any > progress. Watching the handles display, I see an open handle on what > must be the first *.deb file found so I'm pretty sure of the "no > progress -= stuck!" diagnosis. > > Killed it all, ran my scan with the identical sh script in Debian > proper. It did, indeed, take a bit of time but it completed without a > hitch and /bin/rm never stayed long enough for me to see it: perl got > about 3 sec. CPU, dpkg-deb about 2, find about 2, everything else less > than 1. looks some kind of typical windows race condition. give the filesystem some time after rm. haven't got the src of dpkg-scanpackages. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ -- 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/