Red Hat Bugzilla – Bug 71945
RFE: The initial run of updatedb should not be right after installation
Last modified: 2015-01-07 18:59:28 EST
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description of problem: I propose to delay the initial run of updatedb after installation to a later time. A first time user gets the impression of a very slow system when updatedb is running. Even the startup of firstboot takes ages cause updatedb is running in the background. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install (Null) 2. Watch "top" some minutes after the initial install 3. Additional info:
More generically, it often seems to run shortly after boot, and that can be annoying sometimes. It would be neat if updatedb could somehow limit the amount of disk access it does when it runs soon after boot (or maybe even when it runs from the daily cronjob, although that I'm not so sure about). I guess it's too late to do it for this release. (It might be even better to add some kind of "disk-nice" feature to the kernel, but I'm virtually certain it's too late to do it for this release.)
Seems to be fixed since Red Hat 9, so I'm closing this bug now.