John Miezitis wrote:
> 
> I have compiled and installed squidGuard version 1.2.0. on RedHat 8.0 
> using Berkeley DB 2.7.7.

In spite of what the documentation says, squidGuard 1.2.0 requires
version 3.29 of the Berkeley DB (available here:
http://www.sleepycat.com/download/patchlogs.shtml

You can stay with DB 2.7.7 and run squidGuard from the text files.
SquidGuard will simply rebuild the B-trees from the text files each
time it is started. Once the B-trees are built and loaded into 
memory, squidGuard performance is the same, with or without
the db files.  You might want to use that approach to do enough 
testing to know if squidGuard does what you need.  If so, you'll 
definitely want to move to db 3.2.9, creating the db files makes
a tremendous difference in squidGuard's startup time.

If you decide to upgrade, the following checklist has been 
verified on Red Hat:

- - - - - db-3.2.9 upgrade checklist - - - - -
<Download db-3.2.9 from here:>
<http://www.sleepycat.com/update/snapshot/db-3.2.9.tar.gz>
<Copy db-3.2.9.tar.gz to /usr/local/src>
'tar zxvf db-3.2.9.tar.gz'
<Download the two patches for 3.2.9 from here:>
<http://www.sleepycat.com/update/3.2.9/patch.3.2.9.html>
<Copy patch.3.2.9.1 to /usr/local/src/db-3.2.9>
<Copy patch.3.2.9.2 to /usr/local/src/db-3.2.9>
'cd db-3.2.9'
<'pwd' should show /usr/local/src/db-3.2.9>
'patch -p0 < patch.3.2.9.1'
'patch -p0 < patch.3.2.9.2'
'cd build_unix'
'../dist/configure'
'make'
'make install'
'cd ../..'
'echo /usr/local/BerkeleyDB.3.2/lib >> /etc/ld.so.conf'
'ldconfig'
<Copy squidGuard-1.2.0.tar.gz to /usr/local/src>
'tar zxvf squidGuard-1.2.0.tar.gz'
'cd squidGuard-1.2.0'
'./configure --with-db=/usr/local/BerkeleyDB.3.2'
'make'
'make install'
The .db files created with BerkeleyDB cannot be used with
BerkeleyDB 3. If you are using the prebuilt .db files,
rm *.db and do a squidGuard -d -C all
- - - - - - end of checklist - - - - - - - - -

> Has anybody seen this problem before?
http://tinyurl.com/7vlq

Rick




> 
> If I run squidGuard -C to create DB files squidGuard reports that the 
> logfiles are created ok.  The domains.db and urls.db files are indeed 
> created and are not zero length however when I next run squidGuard I get 
> the following messages:
> 2003-03-17 16:17:07 [1313] init domainlist /usr/local/squidGuard/bla
> 2003-03-17 16:17:07 [1313] loading dbfile /usr/local/squidGuard/blac
> 2003-03-17 16:17:07 [1313] domainlist empty, removed from memory
> 2003-03-17 16:17:07 [1313] init urllist /usr/local/squidGuard/blackl
> 2003-03-17 16:17:07 [1313] loading dbfile /usr/local/squidGuard/blac
> 2003-03-17 16:17:07 [1313] urllist empty, removed from memory
> 2003-03-17 16:17:07 [1313] squidGuard 1.2.0 started (1047878227.822)
> 
> Running the perl script from the FAQ's to list the DB files nothing is 
> returned.
> 
> Has anybody seen this problem before?
> 
> Thanks.
> Cheers.
> --JohnM
> 
> 
> 

Reply via email to