Anyone seen this fileresults.db from SCM is increasing in size on linux machine.
How to stop it or control it, since linux/unix machine doesn’t having this much space to handle it.
-rw------- 1 root root 1.6G Apr 19 00:47 fileresults.db
This is generated by the SCA Deploy and Run task.
If you delete the file today, will come back the next time your SCA Deploy and Run policy action re-runs.
Have a look at the action parameter queries for FSTypes and Mount points.
These parameters allow you to exclude fstypes and mountpoints that may be large/shared/be very deeply nested…
When you have identified the large mount points on those systems where filresults.db is more than a couple of hundred MB - then Stop the action, and relaunch it with the new exclusions.
I’m looking for anything that might provide a good guideline for what constitutes “large” or “deeply nested” and how they might be identified by an analysis.