Bug 128701
| Summary: | cron misinterprets files in /etc/cron.d | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ralf Ertzinger <redhat-bugzilla> |
| Component: | vixie-cron | Assignee: | Jason Vas Dias <jvdias> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-06-30 18:45:16 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: | |||
Whoops! Sorry... Yes, the patch to read in /etc/cron.d appears to have been misapplied and incorrectly ran those crontabs as "user" crontabs. This is now fixed ( vixie-cron-4.1-3 ) . Something is still fishy with vixie-cron-4.1-4. Every ten minutes I get the following in the syslog file: crond[xxxx]: Critical error - immediate abort The only possible culprit is the file in /etc/cron.d Actually, the "immediate abort" is the subject of bug 128843, which was fixed today in vixie-cron-4.1-6 - you need to add the line: auth sufficient pam_rootok.so to the /etc/pam.d/cron.d file (or install vixie-cron-4.1-6) - also it's best to install pam-0.77-53. FYI: Same here with vixie-cron-4.1-FC2_1 on FC2, I'll downgrade for the time being. There are no known problems with vixie-cron-4.1-FC2_1 on FC2 - this bug is closed. ISC vixie-cron-4.1 has tightened security restrictions on crontab files: o they must not be writable by any user other than root o they must not be links But lines like: */10 * * * * root /usr/lib/sa/sa1 1 1 work fine, and the "immediate abort" bug is also fixed, but also only happened with FC3/rawhide systems where selinux is enabled. Oh dear - it seems the fix for this bug got dropped when I removed the selinux stuff for the FC2 release - sorry! I'm now generating vixie-cron-4.1-FC2-2 . This is now fixed in vixie-cron-4.1-FC2-2 . |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040625 Description of problem: /etc/cron.d contains one file (sysstat, owned by the sysstat package) It contains, among others, a line like */10 * * * * root /usr/lib/sa/sa1 1 1 According to the man page for cron, this format is correct for the /etc/crontab file and files in /etc/cron.d. However, cron seems to interpret the file like user crontab files, using everything from the sixth field on as the command to be executed, so it ends up trying to execute a command called "root" (which does not exist, of course). Because of this cron sends a mail about this every ten minutes. Version-Release number of selected component (if applicable): vixie-cron-4.1-1 How reproducible: Always Steps to Reproduce: 1. Upgrade to cron 4.1 and have files in /etc/cron.d 2. Wait for execution of one in these files 3. Actual Results: cron treats the user name as commmand to be executed Expected Results: Execution of the program as the user specified Additional info: