Results 1 to 2 of 2
Several times lately, I have found my computer nearly paralyzed---running so slowly as to be essentially unusable. Quick check of system monitor shows updatedb running and using ~97% of CPU. ...
- 08-26-2005 #1Just Joined!
- Join Date
- Aug 2005
- Location
- Pasadena, CA
- Posts
- 14
updatedb locks system
Several times lately, I have found my computer nearly paralyzed---running so slowly as to be essentially unusable. Quick check of system monitor shows updatedb running and using ~97% of CPU. Killing it brings everything back to normal.
I have never messed with any cron settings, and this is the first issue with this setup since it was created many months ago.
Athlon XP2400, ABit MB, 1G ram, Ubuntu 5.0.4
- 08-26-2005 #2Linux User
- Join Date
- Jun 2005
- Location
- USA
- Posts
- 271
Updatedb will use a considerable amount of CPU. This is just a stab, but if it has been running with less noticeable system slow-downs, then I would surmise that you have some directories on your system that are perhaps large or densely populated, and the updatedb command is encountering some sluggish behavior during this time.
Try pruning some of the non-essential paths and/or mounted partitions and then run updatedb again to see if there is any noticable difference. You can prune those directories in the /etc/updatedb.conf file under the title PRUNEPATHS.It may be that your sole purpose in life is simply to serve as a warning to others.
Reply With Quote 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
