Bug 13475 - updatedb shouldn't include nfs as a default
updatedb shouldn't include nfs as a default
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: slocate (Show other bugs)
7.1
All Linux
low Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-07-04 15:25 EDT by Karsten Hopp
Modified: 2014-03-16 22:14 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-07-06 02:36:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Karsten Hopp 2000-07-04 15:25:51 EDT
updatedb -f nfs does the trick, but wouldn't that be better for default ?
Comment 1 Bill Nottingham 2000-07-04 15:29:42 EDT
Hm, possibly. It doesn't include it when run from cron.

Perhaps we should add a default updatedb.conf that does the same thing?
Comment 2 Jeremy Katz 2000-07-06 02:36:21 EDT
If you do this (which would be a good thing... stale nfs mounts can cause
problems in this case), also make sure that afs is excluded.  I believe it is,
but am not 100% certain and pegging every afs server on the planet tends to be a
bad idea :)
Comment 3 Ngo Than 2000-08-23 21:04:57 EDT
now slocate-2.2-5 contains a default updatedb.conf.

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