Bug 128706
| Summary: | crontab: You are not allowed to use this program | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas Zehetbauer <thomasz> |
| Component: | vixie-cron | Assignee: | Jason Vas Dias <jvdias> |
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-08-09 23:13:07 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: | |||
This is not a bug - as the manpage which you quoted states: " If neither of these files exists, only the super user will be allowed to use this command. " That means that if neither /etc/cron.allow nor /etc/cron.deny exist, only the superuser (root) can use crontab. This is new and breaks things, vixie-cron should include and install an empty /etc/cron.deny when updating. should be fixed as of mailman-2.1.5-10 we no longer use crontab, but rather install a mailman cron script in /etc/cron.d, which is not supposed to have the same restriction. This has some other advantages as well. sorry, I edited the wrong bugzilla apparently :-( |
package: vixie-cron-4.1-1 open("/etc/cron.allow", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/cron.deny", O_RDONLY) = -1 ENOENT (No such file or directory) You (thomasz) are not allowed to use this program (crontab) See crontab(1) for more information If the cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the cron.allow file does not exist but the cron.deny file does exist, then you must not be listed in the cron.deny file in order to use this command. If neither of these files exists, only the super user will be allowed to use this command.