Bug 28606 - modutils requires vixie-cron
modutils requires vixie-cron
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: modutils (Show other bugs)
6.2
i386 Linux
low Severity low
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-21 09:14 EST by Binand Sethumadhavan
Modified: 2014-03-16 22:19 EDT (History)
2 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Binand Sethumadhavan 2001-02-21 09:14:04 EST
rpm -q --whatrequires vixie-cron tells me that modutils-2.3.9-6
requires it. IMHO, that is bad - it ties users to one particular cron
implementation. I encountered this while trying to install dillon-cron
on my system.

It would be nice if vixie-cron provided a virtual package like
sendmail/apache etc. do, and other packages used that one.

On second thoughts, why does modutils require a cron daemon at all?
None of the other packages that put files in /etc/cron.* directories
has this requirement (and there are six of them in total on my minimal
RHL 6.2 installation).
Comment 1 Daniel Roesen 2001-02-21 10:21:08 EST
Having a crond is compulsary for auto-removal of unused kernel modules (the kmod
cron job). But I agree that there should be a virtual package "crond".
Comment 2 Bill Nottingham 2001-02-21 11:51:34 EST
We may add a virtual package if we ship a different cron daemon anywhere.

In any case, the requirement is not going away unless the cron script does.
Comment 3 Binand Sethumadhavan 2001-02-21 11:59:53 EST
Agreed, but having a cron daemon is also compulsory for tmpwatch etc. but they
don't have this additional dependency. And anyway, they needn't be tied to
one particular cron implementation.

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