This exact problem was reported in January. The resolution was that the db files are NOT in
/usr/local/squidguard/dest/db but rather in /usr/local/squidguard/squidguard/db/ so change all references accordingly. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of azita m.s Sent: Monday, April 08, 2002 3:42 AM To: [EMAIL PROTECTED] Subject: db problem doesn't solved. hi, thanks for your kindness but my problem doesn't solved. I deleted db-2.7.7 and /usr/local/BerleleyDB ,after that I installed db-3.2.9 and installed squidGuard for another time but it wasn't useful and nothing was created in usr/local/squidguard/db directory. I think that squidguard has used db-2.7.7 during new install yet . also I used your suggestion about using ./configure with some options ,after ./configure ...,make ,make install there were some problems.like: 1-can't write to logfile /usr/local/squidguard/logs I changed the logs dir to log and this problem was solved. 2-can't openconfig file /usr/local/squidguard/squidguard.conf i copied squidguard.conf from conf dir to /usr/local/squidguard and this problem was solved. but after it when i run squidGuard -C all in logfile I see this line: [7171]destblock good missing active content,set inactive [7171]destblock local missing active content,set inactive [7171]init domainlist /usr/local/squidguard/squidguard/db/dest/adult/domains [7171]error db_open:no such file or directory [7171]going into emergency mode please help me. regards azita. __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/
