Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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: <6.1.0.6.0.20041215162208.03ce21e0@mail.reservoir.com>
X-Sender: schweitz AT mail DOT reservoir DOT com
Date: Wed, 15 Dec 2004 16:33:39 -0800
To: astebakov AT yahoo DOT com, cygwin AT cygwin DOT com
From: Eric Schweitz <schweitz AT reservoir DOT com>
Subject: Re: cygwin Digest 15 Dec 2004 23:28:30 -0000 Issue 3998
In-Reply-To: <1103153310.11507.ezmlm@cygwin.com>
References: <1103153310 DOT 11507 DOT ezmlm AT cygwin DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed


That sounds rather familiar... I'm seeing strange "random" accesses
to my drives using find (and other apps) since I upgraded to
1.5.12(0.116/4/2).  I'm seeing this on two machines now, both
an XP machine and a 2000 machine.

BTW, if I stick a floppy in my floppy drive and run find, I get
the following output from filemon.  It also seems to go out over
any network drives and so forth as well [Boo! Hiss!] even though
I'm running find on a directory tree on the local (C:) drive.

4:19:41 PM      find.exe:3344   IRP_MJ_CREATE   A:\     SUCCESS Options: 
Open  Access: All
4:19:42 PM      find.exe:3344   FASTIO_QUERY_BASIC_INFO A:\     SUCCESS 
Attributes: D
4:19:42 PM      find.exe:3344   IRP_MJ_CLEANUP  A:\     SUCCESS
4:19:42 PM      find.exe:3344   IRP_MJ_CLOSE    A:\     SUCCESS
4:19:42 PM      find.exe:3344   IRP_MJ_CREATE   A:\     SUCCESS Options: 
Open  Access: All
4:19:42 PM      find.exe:3344   FASTIO_QUERY_BASIC_INFO A:\     SUCCESS 
Attributes: D
4:19:42 PM      find.exe:3344   IRP_MJ_CLEANUP  A:\     SUCCESS
4:19:42 PM      find.exe:3344   IRP_MJ_CLOSE    A:\     SUCCESS
4:19:42 PM      find.exe:3344   IRP_MJ_CREATE   A:\     SUCCESS Options: 
Open Directory  Access: All
4:19:42 
PM      find.exe:3344   IRP_MJ_QUERY_INFORMATION        A:\     SUCCESS 
FileNameInformation
4:19:42 PM      find.exe:3344   IRP_MJ_QUERY_VOLUME_INFORMATION 
A:\     SUCCESS FileFsVolumeInformation
4:19:42 PM      find.exe:3344   IRP_MJ_QUERY_VOLUME_INFORMATION 
A:\     SUCCESS FileFsAttributeInformation
4:19:42 PM      find.exe:3344   IRP_MJ_CLEANUP  A:\     SUCCESS
4:19:42 PM      find.exe:3344   IRP_MJ_CLOSE    A:\     SUCCESS
4:19:42 PM      find.exe:3344   IRP_MJ_CREATE   A:\     SUCCESS Options: 
Open Directory  Access: All
4:19:43 PM      find.exe:3344   IRP_MJ_CLEANUP  A:\     SUCCESS
4:19:43 PM      find.exe:3344   IRP_MJ_CLOSE    A:\     SUCCESS
4:19:43 PM      find.exe:3344   IRP_MJ_CREATE   A:\     SUCCESS Options: 
Open Directory  Access: All
4:19:43 
PM      find.exe:3344   IRP_MJ_DIRECTORY_CONTROL        A:\     SUCCESS 
FileBothDirectoryInformation: *
4:19:43 
PM      find.exe:3344   IRP_MJ_DIRECTORY_CONTROL        A:\     SUCCESS 
FileBothDirectoryInformation
4:19:43 PM      find.exe:3344   IRP_MJ_DIRECTORY_CONTROL        A:\     NO 
MORE FILES   FileBothDirectoryInformation
4:19:43 PM      find.exe:3344   IRP_MJ_CLEANUP  A:\     SUCCESS
4:19:43 PM      find.exe:3344   IRP_MJ_CLOSE    A:\     SUCCESS




>Message-ID: <20041215202025 DOT 29944 DOT qmail AT web52802 DOT mail DOT yahoo DOT com>
>Date: Wed, 15 Dec 2004 12:20:25 -0800 (PST)
>From: Andrew Stebakov <astebakov AT yahoo DOT com>
>Subject: find command hangs for 20 sec before starting with cygwin1.dll is 
>1.5.12
>To: cygwin AT cygwin DOT com
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>
>Hi,
>
>I just updated my cygwin to latest (version 1.59) and
>cygwin1.dll is 1.5.12.
>I found that "find" command takes a long time to start
>(about 20 seconds). It shows in my xemacs when I load
>ecb and issue igrep-find.
>I replaced the cygwin1.dll with some old version and
>the problem went away (also I had to replace xargs,
>grep and find executables for the old ones).
>
>On another PC the same cygwin with xemacs doesn't show
>the problem.
>Both of them have the VirusScan on. I tried to disable
>the VirusScan but it doesn't fix the problem.
>What can I do fix it? Can I get the previous version
>of cygwin1.dll?
>
>Thanks in advance,
>Andrei


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