You've been bitten by sloppy documentation! ;-) The squidGuard documentation is for a previous version; if you do what it tells you to do it won't work.
Morris Maynard has put together a site to try and cover the hot issues; here's a section that pertains to you: -- Clipped from http://www.maynidea.com/squidguard/faq-plus.html -- Squidguard 1.20 requires version 3.29 of the Berkely db. It won't work with version 2.27, nor will it work with 4.0. The assertion that configure makes about requiring 3.2.* or later is not really correct. SquidGuard needs 3.2.x ( not sure which version is too low) and we know specifically that it works quite nicely with 3.2.9. I have tried it with 3.3.x and it craps out every time. Same with 2.7.7. (Thanks to Robert Nickel for these specifics). (It has been reported that squidguard 1.20 will work with other versions of the db if you are using plain text files for your blacklists; in other words, if there are no *.db files in your blacklist directories. This can really slow down the startup time of squid/squidguard, but otherwise may not be harmful.) Squidguard 1.14, on the other hand, requires Berkeley 2.27. You can have version 2.27 and 3.2x installed at the same time ------------------------------------------------------------- Once you have the correct database version installed, use the -C switch to create the databases and the updates will work like they are supposed to. (By the way, you mentioned a "domain.diff" file; it should be "domains.diff". I'm sorry you had to suffer through the bad documentation! Rick Matthews -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Kiefer Sent: Tuesday, April 02, 2002 2:08 PM To: '[EMAIL PROTECTED]' Subject: DB Problems Greetings! I have installed squidguard (1.2.0) on a test box, and I'm having some problems with DB updates. If I run this config: logdir /usr/local/squidGuard/log dbhome /usr/local/squidGuard/db dest porn { domainlist porn/domains urllist porn/urls } acl { default { pass !porn all redirect http://www.yahoo.com } } The system works fine, but it takes forever to load the databases. Then I run squidGuard -C all to generate the databases, leaving the text file and database in the same directory and I get this: 2002-04-03 13:38:53 [18566] init domainlist /usr/local/squidGuard/db/porn/domains 2002-04-03 13:38:53 [18566] loading dbfile /usr/local/squidGuard/db/porn/domains.db 2002-04-03 13:38:53 [18566] domainlist empty, removed from memory 2002-04-03 13:38:53 [18566] init urllist /usr/local/squidGuard/db/porn/urls 2002-04-03 13:38:53 [18566] loading dbfile /usr/local/squidGuard/db/porn/urls.db 2002-04-03 13:38:53 [18566] urllist empty, removed from memory 2002-04-03 13:38:53 [18566] squidGuard 1.2.0 started (1017862733.178) 2002-04-03 13:38:53 [18566] squidGuard ready for requests (1017862733.185) Now nothing gets blocked, due to the empty domainlist. So then I run this config: logdir /usr/local/squidGuard/log dbhome /usr/local/squidGuard/db dest porn { domainlist porn/domains.db urllist porn/urls } acl { default { pass !porn all redirect http://www.yahoo.com } } And Squid loads quickly and blocks the way it's supposed to, but when I run squidGuard -u on a file named domain.diff I get this: 2002-04-03 13:45:48 [20299] error update dbfile /usr/local/squidGuard/db/porn/domains.db.db. file does not exists, use -C to create I must be missing something... According to the documentation the db updates should be painless. TIA Mike
