Message-ID: <44B460CC.49C960A1@yahoo.com>
Date: Tue, 11 Jul 2006 19:39:08 -0700
From: "Victor E. Vaile, IV" <victorv4 AT yahoo DOT com>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Find working improperly causes updatedb to take forever
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Hello,

	I upgraded my cygwin today from 1.5.19-4 to 1.5.20-1 (along with other various packages to their current versions).  I ran updatedb, and
instead of it taking less than a few minutes, the prompt hadn't returned after several minutes.  I fired up procexp.exe (from
sysinternals.com) and saw that the find.exe process was opening several registry keys in HKCR.  This process was taking between 20-45% of my
cpu as well.  I did a quick test of the following command:

/usr/bin/find / \( -fstype proc \) -prune -o -print0

Sure enough, the find command happily started traversing the /proc registry keys.  I reverted the cygwin base (keeping everything else
installed as is, although I don't know if there are any dependencies that might be reverted automatically) back to 1.5.19-4, and did the
same test, and find exited properly before descending into /proc as expected.  I'm currently using 1.5.19-4 again. :(

	As far as I know the syntax for the find command should work as above.  (I actually made a copy of the updatedb script and changed it to
echo the find command it was using to make sure.)  Anyway, I saw another post to this list with the subject "Updatedb does not finish",
however I didn't see any replies, or updates, and just thought I'd mail the list in case anyone is interested, or has any other insights. 
Thanks.


-Victor


--
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/