Bug 727977
Summary: | SELinux is preventing /bin/systemd-tmpfiles from 'read' accesses on the directory dump. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eduardo Habkost <ehabkost> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 15 | CC: | dominick.grift, dwalsh, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | setroubleshoot_trace_hash:6c618cd87ca804adde46b289a09aadb04a6f20ee8e0fcd5d2b006de7854ef366 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-08-04 19:13:18 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
Eduardo Habkost
2011-08-03 20:19:03 UTC
Where is the dump directory located? In /root? How did systemd_tmpfiles_t no to look there? I had no idea how it was triggered, I never touched any systemd configuration and I don't know why it is trying to access that directory, so I reported it supposing it was an unexpected denial due to some default configuration. But now I noticed that some time ago I created a "dump" directory on /root and then moved it to /tmp, ending up with this: drwxr-xr-x. root root unconfined_u:object_r:admin_home_t:s0 /tmp/dump So it was my fault, sorry for the noise. |