geep <geep_at at (no spam) boursomail.com> wrote:
vmslackware.13.0/20GB.vmdk -> /space3/20GB.vmdk

Or am I missing the blindingly obvious somewhere?

What kind of file system are those /space cq /space3. The version of
slocate, as distributed in slackware, skips the following types of
fs'es:
devpts NFS nfs afs proc smbfs autofs iso9660 udf (autofs = everything
mounted "on demand" by auto mounter).

Most of them are network fs'es as these should be indexed on their
hosts, not all of the clients.

geep <geep_at at (no spam) boursomail.com> wrote:
locate 20GB.vmdk
still only lists:
/mnt/hda9/home/dad/vmslackware.13.0/20GB.vmdk

Another thing to check is the permission OF the files to be located. I
_think_ and this seems to suggest it:
Secure Locate provides a secure way to index and quickly search
for all
files on your system regardless of ownership. It uses incremental
encoding just like GNU locate to compress its database to make
search-ng faster, but it will also check file permissions and
ownership
before displaying matched
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
entries so that users will not see files they do not have
access
to.
that you will not see files you don't have read-access (at least) for.
Try to do the locate as root, it should be able to access all local
files.

Hi Eef,

4/ Am not quite sure how updatedb/locate handles links, or is supposed
to handle links.

The right way, the link is a file, the file linked TO another:
$ ls -l `locate bin/gzip`
-rwxr-xr-x 1 root root 53912 2007-05-07 05:44 /bin/gzip lrwxrwxrwx 1
root root 14 2008-12-15 12:37 /usr/bin/gzip -> ../../bin/gzip so it
finds both the file (/bin/gzip) and the link (/usr/bin/gzip).

I searched for "bin/gzip" to eliminate a lot of other hits, even this
output I had to cleanup a bit as there were 4 other unrelated results
(like the Windows version gzip.exe, which is samba-shared TO MS-Win
clients).
OK. I'm now seeing that locate lists "normal" files and "link" files.

vmslackware.13.0/20GB.vmdk -> /space3/20GB.vmdk

Or am I missing the blindingly obvious somewhere?

Maybe I should try "GNU locate" rather than slocate to see if it has the
same problem.

Have now installed "GNU locate" from findutils 4.4.2. It works fine.

locate 20GB.vmdk
still only lists:
/mnt/hda9/home/dad/vmslackware.13.0/20GB.vmdk

4/ Am not quite sure how updatedb/locate handles links, or is supposed
to handle links.

On Wed, 21 Oct 2009 14:07:03 +0000, geep wrote:

Maybe I should try "GNU locate" rather than slocate to see if it has
the same problem.

Have now installed "GNU locate" from findutils 4.4.2. It works fine.
./configure \
--prefix=/home/dad/findutils
make -j 2
checkinstall

slocate. Slackware defaults in /etc/updatedb.conf Build the database, as
root, using:
updatedb

Search the database:
/usr/bin/locate 20GB.vmdk
/mnt/hda9/home/dad/vmslackware.13.0/20GB.vmdk

GNU locate.
Build the database, as root, using:
cd /home/dad/findutils/bin
./updatedb --output=/home/dad/findutils/locatedb

Search the database:
/home/dad/findutils/bin/locate --database=/home/dad/findutils/locatedb \
20GB.vmdk
/mnt/hda9/home/dad/vmslackware.13.0/20GB.vmdk /space/VM/20GB.vmdk
/space3/20GB.vmdk

So this seems like a bug with updatedb/slocate.

Cheers,
Peter

I'd be interested if anybody else with Slackware is seeing the same
problem.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In order to use this, you should first uninstall slocate (just to fix
some conflictions with the man pages really), and change the slocate
group to mlocate before compiling.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkrgyVEACgkQNj1TaGS9H5JeqACfRL146OJ5uMgbQ2NWmjsMsVqb
GwkAn0md9hzf9UHTLShhlUgeHoJgTbwj
=o71F
-----END PGP SIGNATURE-----