Bug 7718

Summary: Should "makewhatis / updatedb" immediately
Product: [Retired] Red Hat Linux Reporter: Bryce Nesbitt <bryce>
Component: basesystemAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: rvokal
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: 2000-01-13 15:49:40 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 Bryce Nesbitt 1999-12-10 00:19:33 UTC
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.

               -Bryce

Comment 1 Bill Nottingham 1999-12-17 21:03:59 UTC
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 15:49:59 UTC
This should be fixed in Raw Hide with the introduction of anacron.

Comment 3 openshift-github-bot 2016-03-12 01:33:28 UTC
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/e91867dadcb7e014dcf73d944f1864307a884307
Merge pull request #7936 from rhcarvalho/issue7718-build-output-cycle-detection

Merged by openshift-bot