Bug 440594
Summary: | rpm -V error: SELinux context differs for syslog.conf | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Chris Ward <cward> |
Component: | sysklogd | Assignee: | Peter Vrabec <pvrabec> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.7 | CC: | dwalsh, pmatilai |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-09 14:54:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Ward
2008-04-04 09:34:24 UTC
It is checking the SELinux user of the file user_u versus system_u. If you run restorecon -F /etc/syslog.conf it should fix the file so RPM will not complain. This was fixed to not check the user componant in later versions of rpm. so, is this rpm problem? Should I reassign the issue? Exactly what I'm thinking, should this bug be reassigned to rpm then? Should rpm be checking the user of the file user_u versus system_u? I think the problem is the checking at all. rpm -V checking of SELinux context was removed from newer versions or rpm. It is arguable either way, that this is correct behavior, since it does not match the default context. |