https://bugs.kde.org/show_bug.cgi?id=481101
--- Comment #5 from MarkW <instruf...@gmail.com> --- >> Once I reboot, the above is once again deleted from the file and baloo_file >> keeps running. > I don't think it is Baloo thing in that case, something else in the startup > or logon sequence is enabling it. It would be great to track that down. I've been trying to use `auditd` to do this by creating a custom watch rule in `/etc/audit/rules.d/baloorcwatch.rules`: ``` -w /home/mark/.config/baloofilerc -p wa ``` So far, it's a toss-up between `balooctl` and `systemsettings`. I haven't had the time to properly decode the auditd logs to see which one is the culprit at this stage. >I was wondering about the config being overwritten by the system default (hmm, >that could be in "/etc/xdg/baloofilerc" or >"/usr/share/kde-settings/kde-profile/default/xdg/baloofilerc"), but if your >baloofilerc retains its exclusions, then probably not... Yes, the exclusions are retained, so something else is doing this. > Ahhh! I thought "doh!" moments were my thing 8-) You can't (unfortunately for me) claim a monopoly in that department :-) > I assume you have a structure of "copies" under the .snapshots folder and > Baloo will be seeing these files "for the first time" although I'm not sure I > understand the: >> If you do a "baloosearch -i one-of-your-files.txt" do you get a single >> result or many? >> I get a single result. >My naive assumption (without having tried BTRFS snapshots) is that you'd also >find the snapshot copies of your file. Yes, that is odd. I can confirm that after correctly excluding the snapshots, baloo_file still consumes quite a bit of CPU when things get busy on the filesystem, but it is nowhere near as debilitating now that the snapshots are excluded from its ambit. I can now safely leave it enabled. -- You are receiving this mail because: You are watching all bug changes.
