Matej Cepl wrote:
On 2007-05-29, 21:47 GMT, John Dennis wrote:
updated bz with instructions on how to check if setroubleshootd
is running which is the most plausible explanation for why
sealert cannot connect.
Nonsense, of course it is and it was running. sealert has been
now for the last five minutes trying to get connection to
setroubleshootd (or wherever, showing ``Server load'' message all
the time).
and I have put my audit.log on
http://www.ceplovi.cz/matej/tmp/audit.log.bz2
Hmm... I get: 403 Permission denied
That should be fixed and it has been attached to the bug 215722
as well (although, we should really make from it a new bug; this
one used to be around selinux problems with postfix -- which are
not fixed anyway).
Matej
--
fedora-selinux-list mailing list
fedora-selinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-selinux-list
What platform are you seeing these on.
execmem execstack should not be required for setroubleshoot.
Looks like avahi is trying to communicate with dbus running as
unconfined_execmem_t?
You seem to be running a script from hal called hibernate?
--
fedora-selinux-list mailing list
fedora-selinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-selinux-list
