The remote file system is ext3. Upgrading findutils fixed the problem.
Thank you for your time and assistance.
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to [EMAIL PROTECTED] on 8/11/2006 5:52 PM:
>> I've been having problems with "find", and it's hard to search the
>> enti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/11/2006 5:52 PM:
> I've been having problems with "find", and it's hard to search the entire
> mailing list for "find" since it's such a common word. I don't know what
> cygwin package "find" comes in, so I can't se
'type' reporting the first instance of a file that it finds isn't a
problem. However, I will assume that when you run the 'find' command,
that you're finding that the windows version of find is running and not
the cygwin version, and that's your problem.
The windows version of 'find' is found in
Carlo,
At 08:35 2003-02-05, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] schrieb am 31.01.03 16:47:10:
>
> For the archives: No. This is not going to do what the OP wants at all.
> In fact, if there's more than one file named 1000.*, it won't even work
> (find will produce a "find: paths must prec
[EMAIL PROTECTED] schrieb am 31.01.03 16:47:10:
>
> For the archives: No. This is not going to do what the OP wants at all.
> In fact, if there's more than one file named 1000.*, it won't even work
> (find will produce a "find: paths must precede expression" error). For
> details, "info find" an
Ian,
At 06:49 2003-01-31, Ian R. Chesal wrote:
Your syntax is incorrect. Try:
No. Both Franz's and your syntaxes are acceptable. A backslash is
equally useful for protecting the shell glob character '*' as is
surrounding the argument (or just the asterisk) in single or double quotes.
Franz's
For the archives: No. This is not going to do what the OP wants at all.
In fact, if there's more than one file named 1000.*, it won't even work
(find will produce a "find: paths must precede expression" error). For
details, "info find" and "info bash".
To the OP: Is your 1000 directory a symboli
Your syntax is incorrect. Try:
find . -name "1000*"
I just tried in in /tmp on my cygwin installation and here's the output:
$ find . -name 1000* -o -name 1000.*
./1000
./1000/1000.zip
./1000.tar.gz
You can limit the find to just files or directories with
* <[EMAIL PROTECTED]> (03-01-31 09:57 +0100)
> I trie to search file with find an didn't find all the file which should be
> found
>
> I search for all file starting with 1000 an the file 1000.zip in the
> diretory 1000 is not found
> $ find . -name 1000\*
find -type f -name '1000*'
> ./1000.zip
find . -name 1000.*
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 31, 2003 5:57 PM
Subject: Problems with find
Hi folks,
I trie to search file with find an didn't find all the file which should be
found
I search for all file starting with
Assuming none of the files have any spaces in their
names, the following would be faster (and works).
wc -l `find . -name \*.frm -print`
- Barry
-Original Message-
From: Sheryl McKeown [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 2:39 pm
To: [EMAIL PROTECTED]
Subject: Prob
Hi Randall,
Thanks for the explanation and the working version.
Best,
Sheryl
--- Randall R Schulz <[EMAIL PROTECTED]> wrote:
> Sheryl,
>
> [ Non-Cygwin-specific ]
>
>
> Here's how I'd do this:
>
> find . -name "*.frm" -exec wc -l {} ;
>
>
> The result looks something like this
Sheryl,
[ Non-Cygwin-specific ]
Here's how I'd do this:
find . -name "*.frm" -exec wc -l {} \;
The result looks something like this (I changed the ".frm" suffix to
".java" for the purpose of finding some files on my system):
1114 ./DeferredUpdateKB.java
295 ./Definitor.ja
13 matches
Mail list logo
