View Single Post
Old 10-02-2024, 04:28 PM   #5
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,511
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
Final notes and verdict.

Indexer files appeared because dump-stack called dmcc.sh in the same /usr/bin/ location.

I am not really sure why dump-stack was called at all from dump-and-kill-cvm in /usr/bin/ , because it only checks for the file /PRE_GM_DEBUGGING_FEATURES_ENABLED__REMOVE_AT_GMC (which is required to be present by the JB).

Maybe main question is why dump-and-kill-cvm is called at all. But I couldn't find it.

For now, I just did (with mntroot rw/ro around it)
ln -s -b /dev/null /usr/bin/dump-stack

and it stopped from logs and dumps appearing (no more DISABLE_CORE_DUMP files needed).

dmcc.sh says in the header that this script is intended to be present only on debug devices, not on production ones. So, I think it is safe...?
mergen3107 is offline   Reply With Quote