Daniel B. Thurman wrote:
Ok, I have set the level = debug, started setroublesootd and tail'ed
/var/log/setroubleshootd/*.log for about 15-30 minutes and I see
nothing at all. Not a single entry was logged.
Is it consuming 85-95% of your CPU or not?
The log file should not be empty.
I tried to bring up the sealert (or Applications->System-Tools->
SELinux Troubleshooter) and I was not able to get/see the gui
for this application to even come up. It refuses to display
the gui.
Any ideas?
Stop any running sealert with "sealert -q"
Then run it in the foreground with verbose output to the console by
doing this: "sealert -s -v"
What does it tell you?
--
John Dennis <jdennis@xxxxxxxxxx>
--
fedora-selinux-list mailing list
fedora-selinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-selinux-list
