Bug 115168 - pre/post-install scripts should check /etc/cron.allow, crontab fails
Summary: pre/post-install scripts should check /etc/cron.allow, crontab fails
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mailman
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: John Dennis
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-07 16:22 UTC by Robert M. Riches Jr.
Modified: 2007-04-18 17:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-07 21:42:57 UTC
Embargoed:


Attachments (Terms of Use)

Description Robert M. Riches Jr. 2004-02-07 16:22:55 UTC
Description of problem:
Pre/post-install scripts should check cron.allow
before attempting to run crontab.

Version-Release number of selected component (if applicable):
mailman-2.1.1-5

How reproducible:
100% of the one times I tried it.  :-)

Steps to Reproduce:
1. Customize a system by creating /etc/cron.allow.
2. Run up2date and get mailman-2.1.1-5.
3.
  
Actual results:
Four lines of complaints:

You (mailman) are not allowed to use this program (crontab)
See crontab(1) for more information
You (mailman) are not allowed to use this program (crontab)
See crontab(1) for more information

Expected results:
The script should check (and maybe modify) /etc/cron.allow
if it needs to run crontab.  At the very least, it should
check and issue a more informative message.

Additional info:

Comment 1 Nalin Dahyabhai 2004-04-15 05:57:40 UTC
Bug #120912 suggests a fix for a different bug which would also fix
this, I think (not verified).

Comment 2 John Dennis 2004-09-07 21:42:57 UTC
As per bug #120912 mailman no longer uses crontab(1) to install cron
jobs. Now, when the mailman service is started via its init.d script
the crontab file is copied into /etc/cron.d and when the service is
stopped its removed. I believe this addresses the issues in the bug
report and so I'm closing.


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