On 8/28/07, John Vivirito <[EMAIL PROTECTED]> wrote: > > If correct that updatedb is only for locate/slocate commands to update > its database what makes it so important it run daily why not make it run > weekly and have a manual way to run it upon locate/slocate command or > just by using a command like we do with apt-file since they both search > local database AFAIK, This would prevent complaints like this one or the > other ones out there, (im sure im not the only person that has this > issue) most may write it off cause its devel or use forums as per the > link you gave above.
updatedb creates the database, locate searches it. If you want to disable the automatic database updates and run it by hand, that is fine. Most people don't want to to worry about it. To run it by hand, simply execute "sudo updatedb" and enter your password. That will manually update the database. Another option you have is to set the updatedb process to run at another time. Is there a time when your computer is usually on, but you are not using it? By default, the daily cronjob runs at 6:25 AM. If you edit the "/etc/crontab" file as root, you can change the time that those are run. There are a number of guides online that can explain how to edit this file, or a "man crontab" will help. Another consideration is that if your computer is typically not on at that time, anacron may be kicking in to run those jobs. It checks to see if a scheduled job has not run in x (defaults to 1) days, and if not, waits y (defaults to 5) minutes and then runs those jobs. Since you are consistently seeing this behavior at boot, it seems likely that anacron is kicking the job off. If you edit the "/etc/anacrontab" file, you can see anacron's schedule. The first uncommented line looks like "1 5 cron.daily nice run-parts --report /etc/cron.daily". If you change that so that the delay is longer, it will hopefully trigger when your system is less busy. You can do this by changing the "5" to a larger value, say 45 minutes. That way, you should be in your system, most of the programs you are using are loaded to RAM already, and your disk IO will be lower. You can also make the "1" a higher value, which will make anacron wait longer before it runs missed daily cron jobs. While we're looking at this, let's make sure your hard disk is using DMA. If not, that will result in really poor IO performance. Would you run "sudo hdparm /dev/hda" and "sudo hdparm -tT /dev/hda" paste the output into this bug? If your system drive is not "hda", replace that with an appropriate value. -- -Regards- -Quentin Hartman- -- [Gutsy] after this mornings updates gnome took >5minutes to load https://bugs.launchpad.net/bugs/129928 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
