What, in the hopelessly complex chain of process startups, is supposed to start
setroubleshootd? I find it is either not getting started or silently dieing on
my Fedora 12 system. I find I've been getting a bunch of AVCs logged, with no
alert of course, and no way to get those AVCs translated with human-readable
timestamps so that I have the slightest chance of correlating those with
anything else going on in the system. ("sealert -a /var/log/audit/audit.log"
just dies with "NameError: global name 'avc' is not defined".)
The manpage for sealert mentions a GUI browser. That must have been in
somebody's wet dream, because there is no such thing. Regardless of how
sealert is started, the GUI menu discussed in the manpage does not exist.
Again, SElinux turns out to be a bigger pain than anything it is supposedly
protecting against.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
Attachments:
- x.ksh
(text/plain — 921 bytes)