Bug 134089 – crontab -e is broken

Bug 134089 - crontab -e is broken

Summary:	crontab -e is broken

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	vixie-cron (Show other bugs)
Sub Component:
Version:	3
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jason Vas Dias
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	137326 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-09-29 11:51 EDT by Ed Friedman
Modified:	2007-11-30 17:10 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-09-29 12:10:05 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ed Friedman 2004-09-29 11:51:58 EDT

Description of problem:
crontab -e does not work

Version-Release number of selected component (if applicable):
vixie-cron-4.1-11

How reproducible:
Always

Steps to Reproduce:
1.As any user, type:    crontab -e
2.or, as root, type:    crontab -u username -e
3.
  
Actual results:
You (ed) are not allowed to use this program (crontab)
See crontab(1) for more information


Expected results:


Additional info:

Comment 1 Jason Vas Dias 2004-09-29 12:10:05 EDT

Unfortunately, the new CVS migration resulted in some fixes 
being dropped, which causes this problem.
This is now fixed in vixie-cron-4.1-16:
1. If neither /etc/cron.{allow,deny} exist, 
   ONLY root may use crontab (and now may do so!)

2. If no /etc/cron.{allow,deny} exist when the package
   is installed, the %post script will create an
   empty /etc/cron.deny file, thus allowing all users
   by default, the way the old cron used to work.

Comment 2 Jason Vas Dias 2004-10-27 12:35:15 EDT

*** Bug 137326 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.