I have found one awkward feauture (bug?). Maybe this is related to my
distribution but it seems like a bug and I couldn't find any info in the
FAQ/ manuals.
I simply couldn't get squidGuard to work, my squid log kept on complaining
it couldn't open the log and couldn't open the config file. I had checked
a 1000 times whether the ownership and permissions were right. all the
files in /usr/local/squidGuard had permission 660.
First of all, but this isn't the worst: i have a path statement for my log
files which I want only in /var/log and nowhere else. Regardless of this
statement squidGuard now creates TWO logs, one according to the path
setting in my config file and another one (same name) in
/usr/local/squidGuard/log.
Second of all, now it gets worse: squid(Guard) will ONLY accept/read the
files in /usr/local/squidGuard if the permissions are set to 770 and NOT
660. User and group are set correctly, if i reset the files to 660 it's
won't work anymore.
Maybe this is because I run it on a RedHat 6.2 box but smells like a bug
or a vital missing piece of information in the docs.
Anyways check your squid /var/log/squid/cache.log file to see what's going
wrong or not.
A bit off topic but maybe it's useful info (probably is). I found a way
around the db3.3 problem. I installes BOTH db2.7.7 and db3.3. db3.3 was
already on my RedHat 6.2 box because of the upgrade I did to rpm 4.0.x and
couldn'r remove anymore. I just grabbed the db2.7.7. tarball from
Sleepycat and compiled and installed it. It coincides with db3.3 from the
RedHat RPMS's without problems (2.7.7. doesn't automatically install the
binaries just in /usr/local/BerkeleyDB where we need them for SG).
Having this little piece of information in the FAQ might save a lot of
people some time!
Wonder if anybody found a way to have every file run through a
virusscanner before sending it off the client? (Think squirm has a
possibility for this but haven't found it in SG yet).
Cheers!
Remco
On Wed, 8 Aug 2001, Rick Matthews wrote:
> The squid configuration manual can be found here:
> <http://squid.visolve.com/squid24s1/contents.htm>
>
> The link for OPTIONS FOR EXTERNAL SUPPORT PROGRAMS goes here:
> <http://squid.visolve.com/squid24s1/externals.htm>
>
> Search the page for "redirect_program" and "redirect_children".
>
> Look at the Installing squidGuard page here:
> <http://www.squidguard.org/install/>
>
> Search the page for "redirect_program" and "redirect_children".
>
> Rick
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Sam Carleton
> Sent: Wednesday, August 08, 2001 11:16 AM
> To: [EMAIL PROTECTED]
> Subject: getting setup with squid
>
>
> I am simply not with it... I do not see a single word on the web site
> about how to configure squid to work with squidGuard. Can someone point
> me in the right direction?
>
> I am trying to understand the blacklist provided by squidGuard and how
> to use it and the database in general. I am not familary with Berkley
> DB. I have extraced the balcklist.tar.gz into my
> /usr/local/squidGuard/db directory. I see <filename>.db file, does this
> mean that I do not have to create the database files? When setting
> things up in the squidGuard.conf file, by placing:
>
> dest local {
> domainlist blacklists/porn
> }
>
> does squidGuard know that the domain file is
> /usr/local/squidGuard/db/blacklists/porn/domain.db? (Yes, I have the
> path setup)
>
> The configuration section on the web site talks about Prebuild
> databases. If my understanding is correct, the text file is created,
> then I have to run squidGuard with a -C option and the listfilename to
> create the DB. Where should I be running this from? The directory that
> the DB is in? What should the results of this be?
>
> Sam
>
>
