I've just switched over to using squidGuard 1.20 with BerkeleyDB.3.2. The install and configure worked well and squidGuard is now working a lot better than before.
The only trouble I've got now is persuading the db to accept updates. I put a file called domains.diff in /var/squidguard/db/porn and give it the same permissions as other files there. In it are entries along the lines: +sexsite.com -actuallyoksite.com I do /usr/local/bin/squidGuard -u then rm /var/squidguard/db/porn/domains.diff When I test the change www.actuallyoksite.com is still being blocked and www.sexsite.com isn't. Even a squid -k reconfigure doesn't help. If anyone can help me on this I'd be grateful for their advice as I feel that this is the last hurdle to overcome to a fully functioning squidGuard. Thanks, Nigel -- Nigel Pauli - I.T. Manager St. John's School, Northwood, U.K. http://www.st-johns.org.uk/
