X-Spam-Check-By: sourceware.org
Date: Thu, 8 Jun 2006 14:58:17 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Vishwanath_Karthik AT emc DOT com
cc: cygwin AT cygwin DOT com
Subject: Re: Issue with Find command on windows NT
In-Reply-To: <721B8481D73DE047B62D7AB3750F656006B5DB@CORPUSMX30A.corp.emc.com>
Message-ID: <Pine.GSO.4.63.0606081450180.3113@access1.cims.nyu.edu>
References: <721B8481D73DE047B62D7AB3750F656006B5DB AT CORPUSMX30A DOT corp DOT emc DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Thu, 8 Jun 2006, Vishwanath_Karthik wrote:

> Hi,
>      Find command not seems to be working on Network shares on only
> Windows NT.
>      On Windows 2K,Winodws XP and Windows 2003 it seems to be working
> fine.
>
>       The command issued was
>
>       find I:/TREEABC -print
>
>       where "I " is the mapped network drive.

Does "find /cygdrive/i/TREEABC -print" work any better?

>      On All other Windows except Windows NT It displays all the files
> under TREEABC directory recursively.
>
>      But on Windows NT it does not do that.
>
>      Is there any reason for such behavior .Can this be patched up so
> that it works on Windows NT too?

Just a WAG, but try "find I:/TREEABC -noleaf -print" -- you may be running
into inode emulation problems on Windows NT.

Otherwise, please read and follow the Cygwin problem reporting guidelines
at <http://cygwin.com/problems.html>.  There was also a message on this
list from Corinna Vinschen[1] with a program you could build and run on
your system to print the detailed network drive information -- that might
be helpful in diagnosing the problem.
HTH,
	Igor
[1] <http://cygwin.com/ml/cygwin/2006-04/msg00314.html>
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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