By chance I stumbled upon a small modification to any linux system using 
an mlocate/slocate db. Our BackupPC server runs on Centos 5 which by 
default runs 'updatedb' every night. For those of you unfamiliar with 
this program, it creates and modifies /var/lib/mlocate/mlocate.db for 
use with the 'locate' command.

Our /var/lib/mlocate/mlocate.db file had grown to over 2.5GB since it 
was indexing the BackupPC data directory. To avoid this problem, merely 
add the path to the BackupPC data directory into /etc/updatedb.conf in 
the "PRUNEPATHS =" section.

Hope this helps someone out. We backup the /var/ directory on our 
servers (auditing purposes) and this was taking up a bit of space every 
night.

This *fix* also applies to Debian and Slackware though Slackware uses 
slocate instead of mlocate.

-- 
Ryan Manikowski

System Administrator
Proteus, Inc.
rmanikowski AT proteus DOT com
:703.677.8499:




-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/