settroubleshootd massive CPU use
I'm curious is, there ANY reason to run settroubleshootd if your not running a web server? The only documentation I can find about it relates to watching web servers and since this is on my desktop I'm not running Apache. What I am getting is troubleshootd eating up CPU cycles at an insane rate. Enough that it's causing burps with other applications.
I'm running a mostly stock base FC6 distro. Tried to shut it down with chkconfig with no luck. Do I have to mod a SELinux policy somewhere to kill this CPU eater?