Quote:
Originally Posted by mergen3107
Quote:
Originally Posted by jhowell
[*]A process named Minerva for recording and reporting metrics to Amazon.
[*]An app watchdog for the main interface application, possibly to help detect failures.
|
@jhowell
Thank you very much for still doing these deep dives!
Do you think these can be safely disabled by renaming their binaries?
Like we do with other logging
|
I can confirm that disabling the two minerva binaries has worked for me without any unintended side effects.
(Tested on a Kindle Scribe running 5.16.9 and Marek’s hard float jailbreak packages.)
Code:
mntroot rw
ln -s -b /dev/null /usr/bin/minerva_service
ln -s -b /dev/null /usr/bin/minervad
mntroot ro
Before renaming, the folder /var/local/log/minerva/ was being populated with 393kb “entryDs_file_X” files. It has been roughly a week since renaming the files and there has been no activity since. I have yet to observe any negative consequences so far either.
Some miscellaneous documentation things I noted for those curious:
- I saw that the file “/var/local/acs/kvsDefault.db” includes an identifier key: “minerva_anon_customer_id_key”. It appears it is possibly reset by the lipc value of com.acs.minerva resetCustomerInfo
- I found another minerva-related file at /usr/lib/libace_minerva_metrics_api.so
- I haven’t tested yet if the "kppwatchdog" binary can be disabled yet, but I see it is much less chatty in the system logs. In the same all_systems_logs file, over the same period of time, the string “minerva” had a mention in 764 lines vs “watchdog” having 37
- While I primarily use KOreader, I did test downloading a book and using the Amazon reader and didn't notice any problems. Nor any problems with writing on notebooks. I don't have whispersync enabled, so I cannot test if that functionality is impacted
I hope this was helpful!
