you should check if the path (/usr/pkg/squidGuard/db/blacklists/violence/)
is also readable for squid uid/gid and test the command after performing su -proxy Joe a écrit :
I'm running - dragonflybsd 1.4.2 - squid 2.5.3 - squidguard 1.2.0 unpatched - db3.3.11 I've read the conflict problems with this version of db3. I'd like confirmation if this is the problem. it's just a puzzling result ... When run from the command line: /usr/pkg/bin/squidGuard -c /usr/pkg/squidGuard/etc/squidGuard.conf -d 2006-04-17 17:06:17 [37942] init domainlist /usr/pkg/squidGuard/db/blacklists/violence/domains 2006-04-17 17:06:17 [37942] init urllist /usr/pkg/squidGuard/db/blacklists/violence/urls 2006-04-17 17:06:17 [37942] squidGuard 1.2.0 started (1145318777.655) 2006-04-17 17:06:17 [37942] squidGuard ready for requests (1145318777.661) uid:gid for squid are squid:squid. ownership of all the files is set to squid:squid excessively permissive permissions are also set on all the files = og+rw when initiated from within squid: redirect_program /usr/pkg/bin/squidGuard -c /usr/pkg/squidGuard/etc/squidGuard.conf init domainlist /usr/pkg/squidGuard/db/blacklists/violence/domains 2006-04-17 17:16:56 [38011] /usr/pkg/squidGuard/db/blacklists/violence/domains: Permission denied 2006-04-17 17:16:56 [38011] going into emergency mode Thanks,
-- ______________________________ Arnaud FLORENT IRIS Technologies phone: (33) 03 20 65 85 80 fax: (33) 03 20 65 85 81 mailto:[EMAIL PROTECTED] ______________________________
