> What do you suggest now? You've got to dump squidGuard 1.2.1 and go back to 1.2.0.
squidGuard 1.2.1 is worthless, as changes were apparently made to old sources. Here's a comparison of the /src directories in 1.2.0 vs 1.2.1: http://tinyurl.com/8m2k Also, the squidGuard 1.2.0 'configure' file was generated using Autoconf version 2.52. The squidGuard 1.2.1 'configure' file was generated using Autoconf version 2.13. I apologize for pointing you to version 1.2.1. Rick > -----Original Message----- > From: Boniforti Flavio [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2003 4:14 AM > To: 'Rick Matthews' > Subject: RE: Troubles with Berkeley DB > > > > Was BerkeleyDB.4.1 installed from source or RPM? > > From source tarball... > > > Does /usr/local/BerkeleyDB.4.1/lib/libdb.a exist? > > Yes: > lrwxrwxrwx 1 root root 11 Mar 28 14:15 libdb.a -> > libdb-4.1.a > > > Did you notice the author's warning about squidGuard 1.2.1: > > > > "Also note that you should consider this beta code. One thing I > > noticed was that squidGuard with DB 4.1 are many times slower than > > with the previous versions." > > Mmhh.. Actually I wouldn't mind if it would be a bit slower, the main > content filtering activity is being done by our ISP's parent proxy. > > What do you suggest now? > > >
