Bug 450418
Summary: | rsyslog fails to read custom kernel System.map file due to SELinux | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alessandro Suardi <alessandro.suardi> |
Component: | rsyslog | Assignee: | Peter Vrabec <pvrabec> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | dwalsh, theinric |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-14 11:32:57 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
Alessandro Suardi
2008-06-08 02:46:00 UTC
hmm, I really have no clue how to fix this. A plain copy creates the new file following the default behaviour based on the domain of the creating process (cp) and the type of the target directory. Creating a package for your custom kernel might help. Lets ask Daniel if there is some common practise in this. If you copy to a directory which has multiple context residing in it, you need to reset the context your self. There is no easy way for the system to do this. I believe cp/restorecon is the best solution. You could theoretically use restorecond, if this was a common occurrence. You need to think of this the same way you think of DAC, in that you need to make sure the permissions are ok on the file. |