Bug 741870

Summary: No context for cron?
Product: [Fedora] Fedora Reporter: Robin Powell <rlpowell>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dominick.grift, dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-28 15:05:32 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 Robin Powell 2011-09-28 09:10:25 UTC 
I would like to bring https://bugzilla.redhat.com/show_bug.cgi?id=735877 to your attention, and in particular the fact that restorecon doesn't bring /var/spool/cron to a usable state once it's left it (which it does easily).

I may be missing something, but my expectation is that when I run, say, "restorecon -F -Rv /", I will end up with a system that is as working as the alteration of selinux file contexts can make it.  Discovering that this isn't true, and in an area as essential as the operation of cron, is pretty disturbing.

-Robin
Comment 1 Robin Powell 2011-09-28 09:12:52 UTC 
Also, having to run chcon every time I edit apache's crontab (which I do as root since, of course, the apache user can't login, let alone nobody's crontab) is getting really old.  I suspect that may be an issue on cron's end, though?

-Robin
Comment 2 Daniel Walsh 2011-09-28 15:05:32 UTC 

*** This bug has been marked as a duplicate of bug 735877 ***
Comment 3 Robin Powell 2011-09-28 16:58:17 UTC 
Hah! OK, sorry, just wanted to make sure you guys saw it.

-Robin