You're not the first to experience this. I resolved it by also upgrading the
BerkeleyDB to 3.2. It says Sg1.2 is compatible but I get the feeling it's
actually a requirement. Could some developer comment on this?

Regards,
Jan Klaverstijn

----- Original Message -----
From: "Sean O'Neill" <
[EMAIL PROTECTED]>
To: <
[EMAIL PROTECTED]>
Sent: Monday, January 07, 2002 9:57 PM
Subject: HELP !!!! Upgraded to squidGuard 1.2.0 and .db lists are no longer
being read into memory


> K ... I'm a bit frustrated.  I upgraded to squidGuard 1.2.0 (running Squid
> Cache: Version 2.4.STABLE3 on a Solaris 8 system).  I'm still using
> db-2.7.7 because I didn't feel like compiling another program at the time
> (only have a single CPU SS20 - compiles take a while).  Compile,
> installation, etc went fine.  I even deleted all the .db files and
> recreated them using squidGuard -C and updating them with squidGuard
> -u.  .db files back to the original size they were before the upgrade.
NOW
> I'm getting this in the squidGuard log file:
>
> 2002-01-07 13:52:56 [19733] squidGuard 1.2.0 started (1010433176.422)
> 2002-01-07 13:52:56 [19733] squidGuard ready for requests (1010433176.588)
> 2002-01-07 13:52:56 [19734] init domainlist
> /usr/local/squid/squidGuard/db/blacklists/ads/domains
> 2002-01-07 13:52:56 [19734] loading dbfile
> /usr/local/squid/squidGuard/db/blacklists/ads/domains.db
> 2002-01-07 13:52:56 [19734] domainlist empty, removed from memory
> 2002-01-07 13:52:56 [19734] init urllist
> /usr/local/squid/squidGuard/db/blacklists/ads/urls
> 2002-01-07 13:52:56 [19734] loading dbfile
> /usr/local/squid/squidGuard/db/blacklists/ads/urls.db
> 2002-01-07 13:52:56 [19734] urllist empty, removed from memory
>
> What happened ??!!!! Man, I got real used to those cleaned-of-spam-adverts
> web pages and now CRAP everywhere.  Anyone have any ideas ???
>
> -
> ........................................................
> ......... ..- -. .. -..- .-. ..- .-.. . ... ............
> .-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...
>
> Sean O'Neill
>
>

Reply via email to