Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 7718 - Should "makewhatis / updatedb" immediately
Should "makewhatis / updatedb" immediately
Product: Red Hat Linux
Classification: Retired
Component: basesystem (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 1999-12-09 19:19 EST by Bryce Nesbitt
Modified: 2016-03-11 20:33 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-13 10:49:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bryce Nesbitt 1999-12-09 19:19:33 EST
I've walked a number of people through RedHat installs.
Inviariably I say "type man -k <foo>" to find out about
<foo>.  On a freshly installed machine this fails.  Same
for "locate <foo>".

It fails until the machine is left running after midnight.

The install procedure should force the cron jobs to run, so
the machine is ready and complete, fresh out of the box.

Comment 1 Bill Nottingham 1999-12-17 16:03:59 EST
It's a tossup. If you do this, you get the complaint that
the hard drive starts rattling as soon as you boot up.
Comment 2 Bill Nottingham 2000-01-13 10:49:59 EST
This should be fixed in Raw Hide with the introduction of anacron.
Comment 3 openshift-github-bot 2016-03-11 20:33:28 EST
Commit pushed to master at https://github.com/openshift/origin

Merge pull request #7936 from rhcarvalho/issue7718-build-output-cycle-detection

Merged by openshift-bot

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