On Tue, 17 Sep 2002, Rick Matthews wrote: When I first set up squidGuard 1.2.0, it worked with Berkeley db 2.7.7, but only if I didn't use squidGuard -C. In other words, each time I started squidGuard, it had to build its databases. It took a while to start each time, but it worked. Of course, as Rick seems to imply here, every time I used squidGuard -C to pre-build the databases, it failed miserably. Upgrading to db 3.2.9 fixed that problem. I was then able to successfully pre-build the databases.
Craig > And I assume you have used squidGuard -C to prebuild your databases? > > If you are using the .db files then I can't explain the issue with > squidGuard 1.2.0 and the Berkeley db version. > > Based on the replies that I receive (from those who bother to send > them), changing from 1.2.0/2.77 to 1.2.0/3.2.9 is overwhelmingly > successful. > > If the squidGuard/BerkeleyDB combination is not the problem, what > advice would you give to correct the problem these users are > experiencing? > > Rick > > -- Craig Xpressweb Internet Services [EMAIL PROTECTED] http://www.xpressweb.com
