Re: selinux policy update broke setroubleshoot
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Joe Smith wrote:
Joe Smith wrote:
> After the update yesterday (11/2) of the selinux policy, selinux
> exceptions are no longer reported by the desktop setroubleshoot browser.
> ...
Oops--never mind. That was the case yesterday after the update. Today,
after a reboot, all is back to normal. Apparently it was a transient
thing, although I wonder if a reboot should be required for a policy
update, or if there's something else that should be done to re-start the
messaging.
<Joe
Reboot should not be required. I have a feeling something went wrong
with sealert which stopped reporting the errors.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHMIWarlYvE4MpobMRApp6AKC/G2MaCSl0psvhcV0phqifWcTA3QCgo9+o
Y1JqCrB+LrMj6RYY0cFT3Q4=
=sHNE
-----END PGP SIGNATURE-----