:) I think I meant -C and then -u.  Either way I'm getting no errors and
squidguard is running fine on all my servers regardless of what version
db I am running...

locate db returns so much crap it's hard to sort through.... here's what
I can make sense of...

On my redhat servers I have...
db3-utils-3.2.9-4
db3-3.2.9-4
db3-devel-3.2.9-4

so it looks like the right stuff there including the path...
/usr/include/db3


On the mandrake servers this is what I can find...

[root@myserver root]# rpm -qa | grep db
db1-devel-1.85-7mdk
db1-1.85-7mdk
libdb3.3-3.3.11-7mdk
-=> db2-2.4.14-5mdk  <=-  ???


partial excerpt from "locate db"
/lib/libdb-3.3.so
/usr/include/db1

just to check this server...

[root@myserver webmail]# squidGuard -C all
2002-05-02 08:57:51 [9953] squidGuard 1.2.0 started (1020347866.869)
2002-05-02 08:57:51 [9953] db update done
2002-05-02 08:57:51 [9953] squidGuard stopped (1020347871.120)
[root@myserver webmail]# ll
total 16
-rw-r--r--    1 squid    squid         185 Mar 25 12:25 domains
-rw-r--r--    1 squid    squid        8192 May  2 08:57 domains.db
-rw-r--r--    1 squid    squid          24 Mar 26 10:38 domains.diff
[root@myserver webmail]#


Switch to my other mandrake server....

[root@myotherserver root]# rpm -qa | grep db
libdb3.3-3.3.11-7mdk
db1-1.85-7mdk
libdb3.3-3.3.11-7mdk
-=> db2-2.4.14-5mdk <=- ???


partial excerpt from "locate db"

/usr/lib/libdb.so.3
/usr/lib/libdb2.so.3
/usr/lib/libdb.so.2
/usr/lib/libdb1.so.2
/usr/local/BerkeleyDB.4.0/include/db.h
/usr/share/squidGuard-1.2.0/db/casino/domains.db
/lib/libdb-3.3.so

just to check again...

squidGuard -C all

2002-05-02 08:52:17 [11504] init domainlist
/usr/share/squidGuard-1.2.0/db/casino/domains
2002-05-02 08:52:17 [11504] create new dbfile
/usr/share/squidGuard-1.2.0/db/casino/domains.db


So, I think I've got BerkeleyDB 2.4.14 thats actually doing th db work
on these two servers.  Don't ask me why mandrake has been so shabby
about keeping this up to date.  Half the reason I'm trying out the
mandrake distro is that it usually stays a step ahead of redhat for
keeping the kernel and other rpms up to date...I believe squidguard is
even on the distro CD.

In any event, for those who are having trouble, I'd still advise the
3.2.9 release of BerkeleyDB as everyone else has suggested.  RH7.2 and
mandrake 8.2 should come ready to go, although I found mandrake had some
quirks at first with permissions and locations of files and obviously
and outdated db files ;)



-- 
Kevin White, Linux+, A+
Computer Support
Town of Collierville, TN


Reply via email to