Slocate database coverage

[ivanatora]

Hello,
Locate is very usefull tool for quick finding files. The problem I'm facing is that when I update its database:

# /usr/libexec/locate.updatedb

... it appears some filesystems are completely missed.
I'm updating the DB as root - I want when I locate something with my regular user it should be able to dig trough the whole disk space.
The missing filesystems are mounted in the time of the update and the root user definately have read permissions on them.
All 3 affected filesystems are NTFS.

Can you explain that behavior? Do you have any idea how to add these filesystems to locate indexing path?

[Carpetsmoker]

Add the ntfs filesystem to /etc/locate.rc, i.e.:

# filesystems allowed. Beware: a non-listed filesystem will be pruned
# and if the SEARCHPATHS starts in such a filesystem locate will build
# an empty database.
#
# be careful if you add 'nfs'

FILESYSTEMS="ufs ntfs"

[ivanatora]

I had a little doubt to add it as 'ntfs' or 'ntfs-3g', so I tried both, but it seemed NTFS drives are not indexed again. I checked the file system type as mount sees it:

> mount
/dev/fuse0 on /mnt/ntfs (fusefs, local, synchronous)
/dev/fuse1 on /mnt/xp (fusefs, local, synchronous)

So I've added 'fusefs' to /etc/locate.rc, re-run the update script and - voila NTFS drives were succesfully indexed