locate.updatedb breaks on inaccessible smbfs mounts

Bill Hacker wbh at conducive.org
Sat Mar 12 14:45:18 PST 2005

Rumko wrote:

On 2005-03-12, YONETANI Tomokazu <qhwt+dfly at xxxxxxxxxx> wrote:

On Sat, Mar 12, 2005 at 03:02:29PM +0000, Rumko wrote:
On 2005-03-06, Rumko <rumcic at xxxxxxxxx> wrote:

On 2005-03-06, Rumko <rumcic at xxxxxxxxx> wrote:

when a smbfs share is unavailable (the machine is turned off or the samba 

because of this the locate database only contains entries in / up to /mnt/router
and doesnt for example have /usr in it.
so anybody checked this yet?
Isn't it what PRUNEPATHS (in /etc/locate.rc) for? You can add /mnt/router
in the PRUNEPATHS, if you don't care about files under /mnt/router to be
in locate DB.
but, why should I set that PRUNEPATHS if the default for FILESYSTEMS is ufs?
it shouldnt check /mnt/router, cause it isnt ufs!
Not a bug.

Regardless of UFS or {whatever} fs type, if *any* mount-point will contain
removable media or potentially unavailable networked resources.
 (NFS, SMB, AFS, TVS, CD & DVD formats/ devices, etc.)
. .... it should be excluded from  traversal.
Even if it is 'sometimes / usually/ normally' present for the scan,
the db will be unreliable at those times when it is not. Whether or
not it is UFS is not the issue.
Limiting to what is in /etc/fstab, and NOT automounted is a start.....

Couple of examples, complex and simple:




More information about the Bugs mailing list