On Mon, Nov 06, 2023 at 07:15:55PM +0100, Alain Knaff wrote: > But then, shouldn't it keep the shorter path (if both are the root of their > filesystem)?
There's no heuristic that will work in all cases. What is a “shorter” path anyway; is /var/spool/tmp shorter or longer than /mnt/tmp-spool-mount? > And even if it used the longer path, shouldn't it find files which I locate > under that longer path? > > And during investigation, I added /run/schroot to PRUNEPATHS so updatedb > shouldn't have "seen" the longer path at all. The failure to locate files in > my home directory happened both before and after this addition. I assume that it pruned out /run for being a tmpfs (though I haven't checked the logs). I guess the interaction between the prune criteria could be improved, but it's not necessarily trivial, because we don't know the filesystem type until we've started indexing the path. (Anything else opens up a slew of time-of-check-to-time-of-use issues.) All of this logic comes straight from mlocate, FWIW. /* Steinar */ -- Homepage: https://www.sesse.net/
