Summary: | sys-process/vixie-cron Imposes file permission restrictions that are incompatible with sys-process/cronbase | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | William Keaney <keaneyw> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
William Keaney
2010-09-07 17:29:38 UTC
Reading https://bugzilla.redhat.com/show_bug.cgi?id=143191, it looks like this misbehavior is considered a security feature on cron's part. So perhaps the fix needs to go into cronbase? AFAICT cron.d is used to provide files that are in crontab format (with time specification and actions) while cron.{hourly,daily,weekly,monthly} provides full scripts to exec. So the problem is entirely a matter of "you shouldn't be symlinking from cron.d to cron.hourly"... Ah.. hmm. OK. I suppose it was silly of me to assume that it was of the same purpose as /etc/init.d/. However, searching the Web shows that it's a fairly common perception of the purpose of this directory. OK, I looked up RedHat's documentation, and Flameeyes is correct. Files in /etc/cron.d/ take the same format as /etc/crontab, and are meant for scheduling tasks at intervals other than daily/weekly/monthly. |