On Wed, Sep 12, 2007 at 10:36:55AM +0100, Jenny Hopkins wrote:
Hullo there,
There's a script in /etc/cron.daily (on debian-etch server) called 'find', which is starting at around 8.30 am, using 100% cpu power, then kind of sticking there for hours (I just had to manually kill the processes it seems to start, like locate and updatedb and sort). Below is the script, and updatedb.conf.
Has anyone any idea why this should be unable to run properly, and would it be a Bad Awful thing to just have it not run?
Network mounted filesystems? Large backup drive attached?
Add anything that might take "a long time" to run a find over to the PRUNEPATHS in updatedb.conf... even if they should be ignored because of the PRUNEFS setting, remove any network mounts (using PRUNEPATHS too).
If you do disable it, all you'll lose is the "locate" utility, which shouldn't be too big a loss ;)
Hope that helps,