From Fedora Project Wiki
m (moved Bug info SELinux to How to debug SELinux problems: Use plain language titles for searchability) |
(Add to How to category) |
||
| Line 3: | Line 3: | ||
If you encounter a problem where SELinux is denying permission or access inappropriately, include the full text of the AVC message which is logged. This will be in /var/log/audit/audit.log if auditd is running, or otherwise in /var/log/messages. | If you encounter a problem where SELinux is denying permission or access inappropriately, include the full text of the AVC message which is logged. This will be in /var/log/audit/audit.log if auditd is running, or otherwise in /var/log/messages. | ||
[[Category:Debugging]] | [[Category:Debugging]] [[Category:How to]] | ||
Revision as of 11:46, 30 July 2009
This page explains information that should be included when filing bugs related to SELinux. Problems involving SELinux should generally be filed against selinux-policy or selinux-policy-targeted, not the component that is triggering the error.
If you encounter a problem where SELinux is denying permission or access inappropriately, include the full text of the AVC message which is logged. This will be in /var/log/audit/audit.log if auditd is running, or otherwise in /var/log/messages.