I programmatically create a large number of text files. The indexing system immediately tries to index them. As a result, huge memory consumption and 1 processor core constantly working.
At the same time, I absolutely do not need any indexing of the contents of the files.
I tried disabling this service:
[ivan@fedora ~]$ sudo balooctl disable
[sudo] password for ivan:
Disabling and stopping the File Indexer
[ivan@fedora ~]$ balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexing: /home/ivan/Documents/MoscowBase/DOC COMMON BOOKS/Социология права - Шереги/Социология права - Шереги.doc
Total files indexed: 5,093
Files waiting for content indexing: 47
Files failed to index: 0
Current size of index is 5.87 GiB
but as you can see, he refused to complete his work. Deleting a process in the System Monitor doesn’t help either: the process is immediately re-created.
if baloo is run as a service (and it probably is) then you can use
“sudo systemctl disable baloo”
to disable it. I am guessing on the name of the service since I don’t use baloo, but you may be able to find it with
“sudo systemctl list-units”
and parse that for the actual service name.
Since you have balooctl you might be able to control it more directly with its own commands that often can be found with something like “balooctl --help”
Usually disabling does not also stop at the same time. Disabling infers that it will not automatically restart. Stopping involves stopping the currently running instance. Maybe “balooctl stop” would work.