> Interesting. I've found I've had to play a bit with > those permissions. I read the docs (no1 in the FAQ) > as saying user and group needing read and write > [i.e. 660].
Do you have these statements in your squid.conf file? cache_effective_user squid cache_effective_group squid If so, the 640 should work fine. From the configuration page (http://www.squidguard.org/config/), "Notes" section: -------- Clip from Configuration page -------- To avoid publishing to your users a complete guide to banned sites, you probably want to have some or all of these files protected by for instance: chmod 640 /wherever/filter/db/dest/adult/* chown cache_effective_user /wherever/filter/db/dest/adult/* chgrp cache_effective_group /wherever/filter/db/dest/adult/* where cache_effective_user and cache_effective_group are the values for the corresponding tags as defined in squid.conf. -------- End of Clip ------------------------- Whoa! I just realized that I put 740 in my previous post! It should be 640. My apologies. The other important point is that your destination directories should have the same owner and group as specified in your squid.conf for cache_effective_user and cache_effective_group. I have a few questions/comments after looking at your squidGuard.conf file: (1) Your dbhome statement points to /var/squidguard/db. Does the directory name have a lower case "g" to match your dbhome statement? (2) Did you use the blacklists.tar.gz file from the squidGuard site? If you did, and if you installed (unpacked) it using the command listed in the installation instructions, all of your destination directories would be under a /blacklists directory, for example: ${DBHOME}/blacklists/ads ${DBHOME}/blacklists/hacking ${DBHOME}/blacklists/porn etc. Based on your squidGuard.conf, squidGuard will look for your destination directories here: ${DBHOME}/ads ${DBHOME}/hacking ${DBHOME}/porn etc. If that's where those directories are, you probably had to manually move/rename them to get them there. (3) What are the contents of /usr/local/squidGuard/log/blocked.log? Does it have entries for the sites successfully blocked? (4) You mentioned that you were able to get squidGuard started properly. You should be seeing multiple "loading dbfile...", "init domainlist...", "init urllist..." statements in your log file, ending with "squidGuard ready for requests...". Is that what you are seeing? (5) This may be a dumb question, but are you certain that "#" lines in the squidGuard.conf file are considered comments? If I read that I forgot it, and I can't remember ever seeing sample conf files that included comment lines (and they would have been helpful as in-line documentation). Hopefully things are getting better for you? Rick -----Original Message----- From: Nigel Pauli [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 11:21 AM To: Rick Matthews; Squidguard Mailing List Subject: Re: Updating database problem On Monday 04 February 2002 13:52, Rick Matthews wrote: > Would you mind posting your squidGuard.conf file? That would help us > identify the problem. (Feel free to "dummy-up" any private > information.) > > > #chmod -R 770 squidGuard/db/ > > Just thought I'd mention that the documentation only asks for 740 > here. Interesting. I've found I've had to play a bit with those permissions. I read the docs (no1 in the FAQ) as saying user and group needing read and write [i.e. 660]. > Please consider posting your conf file. > > Rick I've attached my squidGuard.conf which lives in /usr/local/squidGuard/. squid.conf has the line: redirect_program /usr/local/bin/squidGuard -c /usr/local/squidGuard/squidGuard.conf Thanks in advance for any ideas anyone comes up with. Nigel > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Nigel > Pauli > Sent: Monday, February 04, 2002 5:28 AM > To: Squidguard Mailing List > Subject: Re: Updating database problem > > On Sunday 03 February 2002 22:50, Rick Matthews wrote: > > squidGuard is fairly verbose in it's logfile; what entries are in > > your squidGuard logfile after the -u command? > > > > Rick > > Good point. In fact I now find out that squidGuard was working > without > actually having any db files at all. Yesterday as I installed I > noticed > that there weren't any *.db files but thought that this was a > feature > of 1.20 and BerkeleyDB 3.2.9 seeing as it worked. > > However, this morning I noticed that squidGuard.log showed no > activity > around bin/squidGuard -u and working on a suggestion from someone > else > I did > # bin/squidGuard -C all > This created all the *.db files but with access denied. Doing > #chown -R squid:squid squidGuard/db/ > #chmod -R 660 squidGuard/db/ > #squid -k reconfigure > got me into emergency mode because of access problems. > #chmod -R 770 squidGuard/db/ > #squid -k reconfigure > got me running properly. Now I thought I'd retry doing > #bin/squidGuard -u > This time squidGuard.log complained that > squidGuard/db/porn/domains.diff didn't exist (even though it did > with > correct permissions) and just hung; when I did Ctrl-C to get the > prompt > back it went into emergency mode. > #squid -k reconfigure > got squidGuard restarted properly but still no update. > > Any advice would be much appreciated. As you can imagine it's all a > bit > frustrating. But, on the positive side, squidGuard is proving to be > good and robust and is not getting stuck in emergency mode. > > Thanks, > Nigel -- Nigel Pauli - I.T. Manager St. John's School, Northwood, U.K. http://www.st-johns.org.uk/
