#19 automounting causes mlocate not scanning anything
Opened 12 years ago by darkraven. Modified 6 years ago

Systemd takes the advantage of autofs to do the 'mount-on-demand', thus leaves to entries in the mount table for one filesystem (one for the real filesystem, one for the autofs). And this behavior results in mlocate skipping the filesystem since autofs is in PRUNEFS (and I actually don't feel it's wrong for autofs to be there).


Thanks for the patch.

I suppose, to be precise, updatedb should base the decision on the "innermost" mount (the one that is actually visible). This information is available only in /proc/self/mountinfo , so fixing this will depend on some other changes (necessary to fix bind mount handling).

Metadata Update from @mitr:
- Issue assigned to mitr

7 years ago

Metadata Update from @mitr:
- Assignee reset

6 years ago

Login to comment on this ticket.

Metadata