On 06/20/2009 06:28 AM, Vadym Chepkov wrote:
All, This is not the very first time I experienced this and I wonder what is the common sense to solving this kind of issues. I installed this policy update: selinux-policy-targeted-3.6.12-45.fc11 Tue 16 Jun 2009 06:29:13 AM EDT Only today I released it made crond in-operational completely for several days. /var/log/cron: Jun 20 06:08:02 hut crond[7705]: (*system*) ERROR (Could not set exec or keycreate context to system_u:system_r:system_cronjob_t:SystemLow-SystemHigh for user) Jun 20 06:08:02 hut crond[7705]: (root) ERROR (failed to change SELinux context) So every single crontab jobs were missed. Simple service crond restart fixes the problem. Do I need to reboot the system every time the new policy is installed, is this the "recommended" approach? Thank you.
No, selinux-policy update should never require a reboot. I have not heard of this before, I have no idea what caused it.
Sincerely yours, Vadym Chepkov -- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-selinux-list
-- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-selinux-list
