Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25347 - [Systemd] special mounting strategy causes mlocate not scanning anything

Attached to Project: Community Packages
Opened by darkraven (darkraven) - Monday, 01 August 2011, 14:07 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 03 August 2011, 03:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
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).

Here is a patch fixing this issue.

Additional info:
* package version(s)
mlocate 0.24
systemd 29

   fix-multiple-mount-entries.pa... (2.4 KiB)
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 03 August 2011, 03:59 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Send your patch upstream.
Comment by darkraven (darkraven) - Monday, 01 August 2011, 14:09 GMT
And I report it here because the author says 'Please consider reporting the bug to your distribution’s bug tracking system.' on his blog.
Comment by Jelle van der Waa (jelly) - Monday, 01 August 2011, 22:12 GMT
Please notice that systemd is in community, so attach it to the project community.
Comment by Dave Reisner (falconindy) - Monday, 01 August 2011, 22:16 GMT
This isn't behavior specific to systemd -- you can have automounting without it. I fail to see why this isn't filed against mlocate, particularly when the patch is for mlocate's updatedb. Better yet, why doesn't upstream want this patch if they consider it a bug?
Comment by darkraven (darkraven) - Wednesday, 03 August 2011, 03:33 GMT
No... This bug shouldn't be tagged '[systemd]', cause it's a mlocate bug. And thus belong to the categroy 'Packages: Core'.

Loading...