Nigel Pauli wrote: > To put this into effect I have user: squid and > group: squid as the owner and group for all > squidGuard files and directories and did: > chmod 440 squidGuard.conf > chmod -R 440 /path/to/squidguard/db
There's your problem - with 440 you've basically write-protected the files; squid cannot write to them. Use 640. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Nigel Pauli Sent: Sunday, January 06, 2002 8:33 AM To: squidGuard list Subject: File and directory permissions I am having problems with getting squidGuard to run sanely and suspect file and directory settings may be a problem. The SquidGuard FAQ says: When run under Squid, squidGuard is run with the same user and group ID as Squid (cache_effective_user and cache_effective_group in squid.conf). The squidGuard configuration and database files must be readable for this user and/or group and the squidGuard log directory must be writable for this user and/or group. If not squidGuard will go into the "pass all for all" emergency mode. To put this into effect I have user: squid and group: squid as the owner and group for all squidGuard files and directories and did: chmod 440 squidGuard.conf chmod -R 440 /path/to/squidguard/db chmod 660 /path/to/squidguard.log chmod 660 /path/to/blocked.log Is this correct? Thanks for any help anyone can give me on this, Nigel -- Nigel Pauli - I.T. Manager St. John's School, Northwood, U.K. http://www.st-johns.org.uk/
