All set. I installed 3.2.9 , with the patches. Then I recompiled squidGuard using the path to 3.2.9. Regenerated my DB files , ran squidguard and all is happy. WOW DB files are fast, thanks Mark. - Nick -----Original Message----- From: Nick Duda Sent: Monday, March 27, 2006 9:29 AM To: Mark Elsen Cc: squid-users@xxxxxxxxxxxxxxx Subject: RE: Reloading squid makes squidGuard go nuts This is squidguard.log below. Also I found an article on the web that points to this problem. So now my question is, how can I tell Berkley 3.2.9 to be used instead of 2.7.7? Squidguard reports "domainlist empty, removed from memory" In spite of what the documentation says, 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. With 3.3.x, 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. My squidGuard version: # /usr/local/bin/squidGuard -v SquidGuard: 1.2.0 Sleepycat Software: Berkeley DB 2.7.7: (08/20/99) My Squidguard.log 2006-03-27 09:05:21 [27825] loading dbfile /usr/local/squidGuard/db/porn/domains.db 2006-03-27 09:05:21 [27825] domainlist empty, removed from memory 2006-03-27 09:05:21 [27825] init urllist /usr/local/squidGuard/db/porn/urls 2006-03-27 09:05:21 [27825] loading dbfile /usr/local/squidGuard/db/porn/urls.db 2006-03-27 09:05:21 [27825] urllist empty, removed from memory 2006-03-27 09:05:21 [27825] init domainlist /usr/local/squidGuard/db/jaits/domains 2006-03-27 09:05:21 [27825] loading dbfile /usr/local/squidGuard/db/jaits/domains.db 2006-03-27 09:05:21 [27825] domainlist empty, removed from memory 2006-03-27 09:05:21 [27825] init domainlist /usr/local/squidGuard/db/whitelist/domains 2006-03-27 09:05:21 [27825] loading dbfile /usr/local/squidGuard/db/whitelist/domains.db 2006-03-27 09:05:21 [27825] domainlist empty, removed from memory 2006-03-27 09:05:21 [27825] squidGuard 1.2.0 started (1143468321.803) 2006-03-27 09:05:21 [27825] squidGuard ready for requests (1143468321.876) -----Original Message----- From: Mark Elsen [mailto:mark.elsen@xxxxxxxxx] Sent: Monday, March 27, 2006 9:18 AM To: Nick Duda Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: Reloading squid makes squidGuard go nuts On 3/27/06, Nick Duda <nduda@xxxxxxxxxxxxxx> wrote: > > > Without doing the .db files it works. Using them now it doesn't. Here is > the conf file, very basic. > - Check squidGuard.log; watchout for any errors. M. --------------------- Confidentiality note The information in this email and any attachment may contain confidential and proprietary information of VistaPrint and/or its affiliates and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may cause liability. In case you have received this message due to an error in transmission, please notify the sender immediately and to delete this email and any attachment from your system. --------------------- --------------------- Confidentiality note The information in this email and any attachment may contain confidential and proprietary information of VistaPrint and/or its affiliates and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may cause liability. In case you have received this message due to an error in transmission, please notify the sender immediately and to delete this email and any attachment from your system. ---------------------
