the program that is running is the updatedb program it updates the locate database. can take quite a while on slower systems(30+minutes sometimes) usually runs around 6am. what it does is finds every file on the system and puts it in an easy to use database see the man page for locate.
it also may run if your system clock was way off and you just updated it, cron may think its been too long since it ran so it runs it. ive seen times when if the clock was off by several months and then updated cron can go nuts and launch everything driving the load to 8 or higher :) it is normal though. im not sure if the locate database is critical or not i just let it run on my systems. i suspect it is not vital to system operation. nate Mike McNally wrote: > > It concerns me when my machine grinds when I don't know why it's > grinding. I run top and it says find is running. Why? I do a grep -r > find /etc/cr* and the only things that come up run per crontab. Crontab > shows that all cron routines run around sunup... it's now 1:42 and my > linux box with a 24hr old install of debian was grinding at 1:10. > Running ls -l /bin | grep rws I get: > -rws... root root for login mount ping ping6 su umount > > Are all of these programs normally setoid? > > mike > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
