Summary: | =sec-policy/selinux-*-9999 needs allowance for fcron to unlink /var/spool/cron/lastrun/lock | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Brandt (RETIRED) <alunduil> |
Component: | SELinux | Assignee: | SE Linux Bugs <selinux> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alex Brandt (RETIRED)
![]() It is very strange that the label is var_spool_t. Was this lockfile perhaps created when the labels were set incorrectly? Try setting it to crond_tmp_t for now (although I would use system_cronjob_lock_t, but there doesn't seem to be a transition for this type yet) and see if the file eventually gets its label back to var_spool_t. May have been an ephemeral issue as you pointed out. I simply removed the lockfile, relabeled the filesystem and cron has been running smoothly since. I'll bring it back up if it starts acting strange again (perhaps it is only certain jobs that leave it in this state). Ok, i'll mark it as WORKSFORME for now |