Bug 2097889 - [RFE] ignore cachefilesd by default
Summary: [RFE] ignore cachefilesd by default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: plocate
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zbigniew Jędrzejewski-Szmek
QA Contact:
URL:
Whiteboard:
Depends On: 2097886
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-16 20:20 UTC by Pat Riehecky
Modified: 2022-10-06 19:36 UTC (History)
5 users (show)

Fixed In Version: plocate-1.1.16-2.fc38 plocate-1.1.16-2.fc37 plocate-1.1.16-2.fc36 plocate-1.1.16-2.fc35
Clone Of: 2097886
Environment:
Last Closed: 2022-08-17 11:58:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pat Riehecky 2022-06-16 20:20:23 UTC
+++ This bug was initially created as a clone of Bug #2097886 +++

Description of problem:
/var/cache/fscache is the default cache directory for cachefilesd.  Similar to caching for other applications, these files make no sense to be indexed by default.

Version-Release number of selected component (if applicable):
mlocate-0.26-300.fc36

How reproducible:
100%

Steps to Reproduce:
1. mount something with `fsc`
2. load some files
3. run updatedb

Actual results:
cache stubfiles are put into the db

Expected results:
these would be ignored

Additional info:

Comment 1 Zbigniew Jędrzejewski-Szmek 2022-08-17 11:38:11 UTC
I added updatedb.conf with 
PRUNEPATHS = "/dev /sys /proc /run /var/cache"

I don't think it makes sense to index anything under /var/cache.

Comment 2 Fedora Update System 2022-08-17 11:58:27 UTC
FEDORA-2022-70a7ad982a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-70a7ad982a

Comment 3 Fedora Update System 2022-08-17 11:58:51 UTC
FEDORA-2022-70a7ad982a has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2022-08-17 11:58:52 UTC
FEDORA-2022-af20cf06e0 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-af20cf06e0

Comment 5 Fedora Update System 2022-08-17 12:01:51 UTC
FEDORA-2022-af20cf06e0 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2022-08-17 12:02:51 UTC
FEDORA-2022-06b128cd5f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-06b128cd5f

Comment 7 Fedora Update System 2022-08-18 02:55:19 UTC
FEDORA-2022-c2e36d044e has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c2e36d044e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c2e36d044e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-08-18 03:30:35 UTC
FEDORA-2022-06b128cd5f has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-06b128cd5f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-06b128cd5f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-08-20 01:44:46 UTC
FEDORA-2022-c2e36d044e has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-08-25 16:17:49 UTC
FEDORA-2022-06b128cd5f has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Jonathan Wakely 2022-10-06 19:36:01 UTC
Does updatedb.conf really need a comment pointing to this bug though?


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