The squidGuard documentation says: ------------------------------- Prebuilt databases Creating a prebuilt database To convert a domainlist or urllist from plain text file to a prebuilt database use:
squidGuard -C listfile and send Squid a HUP signal to respawn squidGuard. Note: listfile is the absolute plain text filename or relative to dbhome. Updating a prebuilt database To add and remove entries from a prebuilt database in runtime put the changes in a diff file (file.diff for file.db) with the following simple format: +new -old ... Then use: squidGuard -u and remove the diff files. The changes should take effect immediately. ------------------------------- squidGuard will function perfectly without the .db files. Prove it to yourself - delete or rename the .db files and <squid -k reconfigure>. Here's the way I understand things: One of the main reasons that squidGuard retains its speed (even with very large numbers of domains and urls), is that it stores all of the domains and urls in B-trees. (See <http://whatis.techtarget.com/definition/0,289893,sid9_gci508442,00.html >) At startup, squidGuard will look in the directory for domains.db and urls.db. If it does not find them, it will look for the text files domains and urls. If it finds those, squidGuard will create a run-time B-tree structure from the text files (the time required to create the B-tree is determined by the number of entries in the text files) and go into operation. When squidGuard is stopped, that B-tree structure is lost and will be recreated during the next startup from the text files. Running <squidGuard -C> tells squidGuard to create the B-tree structures using the text files, and then store those B-trees as domains.db and urls.db. The next time squidGuard is started there is no time wasted on created the B-trees; the db files are immediately loaded and squidGuard is ready to roll. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Henry Barker Sent: Friday, November 02, 2001 10:21 AM To: [EMAIL PROTECTED] Subject: Question about lists I have a question about the lists themselves. In the db directory of a given list (as I have SG configured) are four files that seem to matter in the everyday operation of SG. These appear to be domains, domains.db, urls, and urls.db. Let's say I make a "diff" file in the porn db directory. I run my "squidGuard -u", and all is groovy. Whatever I added or deleted has taken effect. All is well. What I have noticed-- and this may be my own lack of observation-- is that, while the db file gets updated, the text file does not. That is, if I remove "cnn.com" from a list, the db file (which appears to be what is relevant in terms of allowing or blocking access to a site) is updated. If I less the corresponding text file, cnn.com remains in the text list. My question is, based on some exchanges I have been seeing on the ML lately, what role do the text files play in SG's filtering function? Though it might be mistaken, my presumption has always been that the text files are there for the human, so that he or she can see what is in the db files. Certain comments in certain threads of late do not necessarily corroborate this presumption. Anyone. . . ? Anyone. . . ? Cheers, Henry
