Bug 155184
Summary: | SELinux and Cron Daily Issue | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ryan Skadberg <redhat> |
Component: | selinux-policy-targeted | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-20 15:00:05 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
Ryan Skadberg
2005-04-17 19:26:12 UTC
Actually, seeing this in cron.hourly, cron.daily and cron.weekly This looks like a labeling problem. cron should be running under crond_t. What is /usr/sbin/crond context? ls -lZ /usr/sbin/crond -rwxr-xr-x root root system_u:object_r:crond_exec_t /usr/sbin/crond If it is not this, restorecon -v /usr/sbin/crond should fix it. If you want to relabel the system touch /.autorelabel reboot This seems to have been the issue. Doing the restorecon fixed things. I did a relabel just in case other things were broken and all seems well now. Someone probably needs to look in to why this permission got changed for me. Or maybe any selinux upgrade should automatically add a /.autorelabel? Did you ever turn off SELinux? Nope. Process was: Installed FC3 Yum Update to Development Problem started Well the rpm is supposed to figure out what requires a relabel and relabel on the fly. Something must have gone wrong during the upgrade. Did you see lots of restorecon messages during the upgrade? |