1. Hmmmm, never noticed this before, cache.log says the following:

2002/11/09 16:33:28 helperOpenServers: Starting 4 'squidGuard' processes
2002/11/09 16:33:28 WARNING: Cannot run
'/usr/local/squid/squidGuard/bin/squidGuard' process

2. redirect_children = 4 and redirector_access is undefined (ie using
the default ( I hope!)

3. SquidGuard's log file shows no entries when I try load it from
squid.  When I load directly from the command line however, the log says
it's ready to receive requests.

I'm going to carry on plugging away with the cache.log to help (never
bothered looking there before :) ) but please keep the help flowing :)

On Sat, 2002-11-09 at 20:13, [EMAIL PROTECTED] wrote:
> What does cache.log said ?
> Look for the line "helpOpenServer ......"  .
> Did you configure redirect_children ?
> What does squidguard's log file said when you starting it from squid ?
> 
> Quoting Mark Shearar <[EMAIL PROTECTED]>:
> 
> > Hi, I've been struggling with this for the last couple months now on and
> > off and am about tearing my hair out so help would be greatly
> > appreciated.  My squid acts fine and is currently on version 2.5 STABLE
> > 1.  SquidGuard is 1.2.0 with BerkeleyDB 3.2.9.
> > 
> > In the squid.conf the redirector line is:
> > redirect_program /usr/local/squid/squidGuard/bin/squidGuard -c
> > /usr/local/squid/squidGuard/squidGuard.conf
> > 
> > THE PROBLEM:
> > Squid is not, repeat not, starting squidGuard.  The owner and group of
> > the entire squidGuard directory is proxy, which is the same as the
> > effective user and group of squid.  If I start squidGuard from the
> > command prompt it starts fine and the log file shows it's 
> > ready for requests.
> > 
> > I'm not sure where the problem lies anymore.  Squid works fine without
> > the redirect line in, but blocks everything with the redirect line
> > inserted (as there's no squidGuard process running to redirect to!)
> > 
> > Please, please, for the sake of my rapidly balding head, any help will
> > be appreciated!
> > 
> > 
> > 
> > 
> 
> 
> 


Reply via email to