On Fri, 2021-08-20 at 02:59 +0930, Tim via users wrote:
On Wed, 2021-08-18 at 18:59 +0200, Francis.Montagnac(a)inria.fr wrote:
> Commenting PRUNE_BIND_MOUNTS = "yes" in /etc/updatedb.conf solves
> this problem.
So, does that mean it'll also scan through other areas it shouldn't?
Or are the other prunes enough to take care of them? (I just
couldn't
resist referring to them that way.)
I modified the PRUNEPATHS variable to mask my VMs directory, just to be
on the safe side.
poc