Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
updatedb runs once a day by default (on slackware at least) to update the database - it shouldnt be running all the time. try looking in /etc for things related to 'cron', cron is a little daemon which sits there and runs programs at specified times, this is probably setup to run 'updatedb' periodically.
If you don't use locate then I suppose you don't need updatedb running. You can simply delete the slocate entry from /etc/cron.daily, but it doesn't really do much harm to leave it (unless it's interfering with something else) and you may want to use locate some day. It's much faster than find at searching for files by name.
If your machine is on 24 hours a day like most linux machines are (at least from my experience, most linux desktop users do seem to live their machine on) then running updatedb via cron at midnight (or whatever time you're not using your machine) is very useful, since this ensures your slocate database is fairly up to date :) - fast searching as mentioned above.
I was getting nuts in finding where the Locate/UpdateDB configure their autoexecution. On one side the man and GNU documentation of the FINDUTILS, seems to be out of date cause it shows "November 1994". I use SuSE Linux and the findutils package has to be requested during installation, as it's not installed by default.
Ok, once installed, yes, updatedb runs everyday to update the /var/lib/updatedb database, though, it's very annoying if you dont leave the machine on overnight; the updatedb runs automatically after boot as well, because of the /etc/cron.daily/updatedb script . Some sites mention an UPDATEDB.CONF file, but there is no such a thing, and I did not find a reference on the syntax of that file.
But the updatedb script in /etc/cron.daily does a validation at /etc/sysconfig/locate (which is the true configuration file and not updatedb.conf) and takes a bunch of variables from there, which determine wheather there will be an updatedb every day and with wich options of updatedb (those you do can find in either man, info --help for updatedb and in the /etc/sysconfig/locate file).
This way, you can manually run updatedb when you wish and avoid the auto thing by setting RUN_UPDATEDB=no in the configuration file OR move the updatedb script from cron.daily to cron.weekly with RUN_UPDATEDB=yes instead.