Hi,
I have a recent installation of F34 with the default brtfs and I discovered that updatedb and locate don't see the files in /home.
Is there a workaround for that?
G
On Sun, 2021-09-05 at 14:09 +0200, GianPiero Puccioni wrote:
I have a recent installation of F34 with the default brtfs and I discovered that updatedb and locate don't see the files in /home.
Is there a workaround for that?
There was a thread about this a few days back, about allowing bind mounts to be traversed in the /etc/updatedb.conf file. The suggestion was to comment out the prune bind mounts option. I'd suggest that rather than do that, change the "yes" option to a "no," so you explicitly set the desired behaviour, rather than rely on default options set elsewhere (that might change).
See if that helps you.
On 05/09/2021 14:33, Tim via users wrote:
On Sun, 2021-09-05 at 14:09 +0200, GianPiero Puccioni wrote:
I have a recent installation of F34 with the default brtfs and I discovered that updatedb and locate don't see the files in /home.
Is there a workaround for that?
There was a thread about this a few days back, about allowing bind mounts to be traversed in the /etc/updatedb.conf file. The suggestion was to comment out the prune bind mounts option. I'd suggest that rather than do that, change the "yes" option to a "no," so you explicitly set the desired behaviour, rather than rely on default options set elsewhere (that might change).
See if that helps you.
Yes, that seems to work, thanks. Are there any adverse consequences I should look for?
G
On Sun, 2021-09-05 at 17:20 +0200, GianPiero Puccioni wrote:
Yes, that seems to work, thanks. Are there any adverse consequences I should look for?
I asked the same question previously, and don't recall getting told about any.
Elsewhere in that configuration file, there are specific filepaths to not traverse through. They ought to take care of all things that might be a problem.