Re: setroubleshootd using excessive memory
On Fri, 2007-08-31 at 23:28 +0000, Martin Ebourne wrote:
Just noticed a problem with my laptop fully using swap and a major
culprit seems to be setroubleshootd. From top it appeared to be using
excessive vsize:
Would you do me a favor to help diagnose this and check two things for
me?
1) Do a wc on /var/lib/setroubleshoot/audit_listener_database.xml
(you'll need to be root).
2) Open the sealert browser and see if you've got any alerts with very
high counts, or an excessive number of alerts.
Thanks!
--
John Dennis <jdennis(a)redhat.com>