By the way, I would prefer if crond would just die in cases like this. Sincerely yours, Vadym Chepkov --- On Sat, 6/20/09, Vadym Chepkov <chepkov@xxxxxxxxx> wrote: > From: Vadym Chepkov <chepkov@xxxxxxxxx> > Subject: daemons and policy update > To: "Fedora SELinux" <fedora-selinux-list@xxxxxxxxxx> > Date: Saturday, June 20, 2009, 6:28 AM > 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. > > Sincerely yours, > Vadym Chepkov > -- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-selinux-list
