Bug 16608
| Summary: | /etc/cron.d/kmod is evil! | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Kenneth Topp <ken> |
| Component: | modutils | Assignee: | Michael K. Johnson <johnsonm> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | ||
| 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: | 2000-10-03 17:45:13 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: | |||
|
Description
Kenneth Topp
2000-08-19 21:36:39 UTC
I want to update the severity, as this isn't that important (work around is just to comment out the cron job). I just think that as hardware pops in and out of the system, the freeze on an rmmod is not worth the 20k of memory gained, by default. /etc/cron.d/kmod is removed in 7.2. |