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. Please consider posting your conf file. Rick -----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/
