On 2024-11-16 03:45, David C. Rankin wrote:
On 11/15/24 1:05 PM, Carlos E. R. wrote:
I have rebooted the machine, and so far the things are gone (and I put a ".trackerignore" file in there). I'll keep your idea in mind.
Problem would be, each process lives for less than a second, then another is started searching for a different file.
ps afx might see the parent, but the processes I saw were in parallel, not hanging one from another.
Do you like tracker?
I tried to make friends with desktop search starting from the dreaded- dog beagle on, but I haven't ever found them useful. There are times when I wish there were something that was light (on resources and index size) and would find exactly what I can't recall where in my normally strong directory struct that tidbit landed.
I've found normal utilities much more friendly, find, grep, plocate, etc.. They have done the job for me. It's never an important document that gets lost, it's usually a note I've put in a Readme-something.txt that's a bit too long for basket (generally shorter than a page of text gets organized there).
I've tried opensearch and at least a half-dozen others. But not Gnome anything any longer. So if you have a "killer search app" that fits the bill, I'm open to trying another out. But I always found tracker much like beagle and it meets the same fate on all my boxes (as a plus, I never have to worry about it spamming the journal :)
No, I don't have a killer search app, it is just that tracker comes with XFCE (because it uses gnome things). It doesn't always find what I want, and as it is not often that I use it, I always have to relearn it. I use 'mc' which can do a massive grep on files. Takes an awful time, and searching LO documents is useless. I am testing now recoll, that Masaru uses, but it is KDE oriented, dunno if it will work with XFCE. As I started the indexing with default values from a terminal, I can see what it is indexing. I see it wasting time with /home/cer/LOG_imapsync/, so I open the config to exclude that directory; but it continues indexing the path. Seems to ignore configuration changes done while indexing is running. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)