Bug 436205 - nfs mounts excluded by default
Summary: nfs mounts excluded by default
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mlocate
Version: 8
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-05 21:27 UTC by Walter Neumann
Modified: 2009-12-12 16:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-05 21:32:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Walter Neumann 2008-03-05 21:27:35 UTC
Description of problem: The daily cron job mlocate.cron excludes nfs and nfs4
mounts. 


Version-Release number of selected component (if applicable):
mlocate-0.18-1

How reproducible:


Steps to Reproduce:
1. Run updatedb from the daily cron job (or run mlocate.cron directly)
2.
3.
  
Actual results:
nfs mounts are excluded.

Expected results:
nfs mounts should be included if not excluded in updatedb.conf


Additional info:

The option of excluding nfs mounts should be transparent to the user and should
therefore be in /etc/updatedb.conf, where the user expects to find it.

Adding "|grep -v nfs" as follows to the second line of mlocate.cron removes the
exclusion of nfs mounts.

nodevs=$(< /proc/filesystems awk '$1 == "nodev" { print $2 }'|grep -v nfs)

But, IMHO, this whole line should be deleted, or moved to updatedb.conf.

Comment 1 Miloslav Trmač 2008-03-05 21:32:20 UTC
Thanks for your report.

Running (updatedb) over the network is very inefficient, and excluding all nodev
filesystems is a simple way to exclude all network file systems.

mlocate should support network filesystems better in the future; this is tracked
as bug #221756.

Comment 2 foudfou 2009-12-12 16:13:35 UTC
IMHO, there should be a mean to include (still) the excluded network filesystem. /etc/updatedb.conf seems to be the appropriate place.


Note You need to log in before you can comment on or make changes to this bug.