Fast find won't in 3.0

Thread View: comp.sys.next.sysadmin

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Fredrik Nyman Thu, 01 Oct 1992 15:11

#1676

Author: Fredrik Nyman
Date: Thu, 01 Oct 1992 15:11

14 lines
1068 bytes

Every night at 2 AM, I run /usr/lib/find/updatedb to update the fast
find database (/etc/find.codes in 3.0).  However, to my great dismay,
it seems that using fast find (i.e. "find filename") doesn't work
anymore.  No matter what filename I enter on the command line, find
produces no output.  I checked that /etc/find.codes was world readable
(it was) and that it was non-empty (it was; ls reported its size as
~200K).  Frustrated, I su'd to root, mv'd /etc/find.codes to
/etc/find.codes.old, cd'd to /, and ran /usr/lib/find/updatedb.
After some 15 minutes, updatedb completed and there was a nice new
/etc/find.codes, also ~200K.  BUT fast find still wouldn't work.

ARGH!

Does anyone else have this problem?

Re: Fast find won't in 3.0

#1694

Author: Meinhard E. Mayer (Hardy)
Date: Fri, 02 Oct 1992 05:35

13 lines
1142 bytes

In preparation for the update to 3.0 (and the news that find stopped
working), i got and compiled gnu find3.07.  Except from a slighly
different directory structure  (find.codes is now kept in
/usr/local/lib/locate)it works fine.  One caveat however: if you have
NFS mounted disks, it may be necessary to remove these from the
updatedb script; otherwise the sorting and hashing may fill up an
already swol;len swapfile. 

--
Hardy 
-----
Meinhard E. Mayer,  Department of Physics, UC Irvine 
e-mail: hardy@golem.ps.uci.edu (preferred) or MMAYER@UCI.BITNET

Re: Fast find won't in 3.0

#1695

Author: Moises Oliveira
Date: Fri, 02 Oct 1992 08:03

30 lines
1498 bytes

In article <HARDY.92Oct1223541@golem.ps.uci.edu> hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) writes:
>In preparation for the update to 3.0 (and the news that find stopped
>working),

Find has always used regexp (that's regular expression) to search for files
when using both the normal method and fast find.

In the past, the fast find has always accepted an impled star (* == match
anything) on both ends of the expression.  So if you typed

find myfile

Find would translate that to

find *myfile*

With the current version of find you must place your own stars on the
expression.  Since you (whoever is reading this) are probably using csh, you
will probably need to escape the stars.  So you would type.

find \*myfile\*

or

find "*myfile*"

This new method allows you to do things like 
find ~/\*.m | more
which will show you all .m files inside your home folder (instead of all 
.m files, everywhere on the hard drive)

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads