Bug 1929
Summary: | RFE: more intelligent makewhatis.cron | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Siebenmann <cks-rhbugzilla> |
Component: | man | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | ||
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: | 1999-04-09 23:29:16 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
Chris Siebenmann
1999-04-01 08:18:37 UTC
Thank you for your suggestion. This has been passed on to a developer. Seems like a weekly script to rebuild the database and a daily script to update the database would be about right... Fixed in man-1.5g-2. makewhatis already had a -u option for doing fast updates to the database. There's now a weekly script that recreates the database and a daily script that updates it very quickly. makewhatis itself already had all the needed intelligence -- we just needed to harness it. We wouldn't want to avoid rebuilding the database once a week because the updates aren't sorted, just appended, and over time an actively-maintained system would end up with a rather messed-up database providing essentially random apropos output... Thanks for the suggestion! |