BUG: Cygwin implementation of Debian package tools
David A. Cobb
Superbiskit@cox.net
Fri Oct 29 17:33:00 GMT 2004
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.
--
David A. Cobb, Software Engineer, Public Access Advocate
"By God's Grace, I am a Christian man; by my actions a great sinner."
-- The Way of a Pilgrim: R.French, Tr.
Life is too short to tolerate crappy software!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Superbiskit.vcf
Type: text/x-vcard
Size: 261 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20041029/49b21dde/attachment.vcf>
-------------- next part --------------
--
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/
More information about the Cygwin
mailing list