Red Hat Bugzilla – Bug 467482
sealert should exit if setroubleshoot isn't running
Last modified: 2009-09-14 15:45:21 EDT
If setroubleshoot isn't running, sealert should probably exit to save resources
The problem is what happens when someone
# service setroubleshoot restart
I guess the real goal would be to make the applet a lot less of a resource hog. If we just rewrote the applet in C and then launched the python browser when someone clicked on it, would that save lots of memory?
Patches accepted. :^)
I also don't believe it should be running on all desktops, for managed desktops the applet should probably not run at all.
If they start setroubleshoot after they've already logged in, then they get sealert on the next login. It doesn't really feel like a case to optimize for :)
One problem with that is we want to move to a dbus type service.
Avc comes in, audit starts setroubleshoot and sealert gets notified.
THe real problem is that applets should be light weight.
Dan, are there any plans to resolve this? If not, please close WONTFIX.
sealert is now a lightweight applet that starts setroubleshoot on demand.
So I would say this is fixed in F11.