I did play around with that squidGuard -C all command before. I ran into an issue where it would finish and shutdown all the squidGuard processes when it completed, or so I was led to believe in the log. I'm sure it was some odd timing issue where I had multiple processes starting before it actually completed.
How does one schedule that? The -C all command, do you run that before squid starts as a differeint init script? Also, if you have them prebuilt, how do you 'rebuild' them again and not take down all the squidGuard proccesses? -- Dave Mullen "He who would sacrafice liberty for safety deserves neither liberty nor safety." -Benjamin Franklin ---------- Original Message ----------- From: "Brian Gregory" <[EMAIL PROTECTED]> To: "Dave Mullen" <[EMAIL PROTECTED]>, <[email protected]> Sent: Wed, 2 Aug 2006 22:57:11 +0100 Subject: Re: [squid-users] squid -> squidGuard: Redirect_children best practice? > ----- Original Message ----- > From: "Dave Mullen" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, August 02, 2006 8:32 PM > Subject: [squid-users] squid -> squidGuard: Redirect_children best practice? > > > Hey folks, > > > > I'm finding people with different opinions talking about the > > redirect_children > > option from within squid. > > > > One is to set it to something like 5, so that you have plenty of ability to > > answer ( like apache? ) and the second is to limit squidGuard children to > > have > > an equal amount of processes as CPU's in the box. > > > > I've got a company with ~500 employees that this will be blocking with a > > fairly large blacklist. My big concern to this is time from post to proxy. > > With multiple processes starting it seems to dramatically build the time up > > it > > needs to get to full start. > > > > Thoughts? > > Are you "pre-compiling" your domainlists and urllists into *.db > files by doing: > > squidGuard -C all > > ?? > > If not that will greatly speed up the start-up time when there are > many squidguard processes starting up. > > How are you blocking with https:// URLs?? > > I find blocked https:// URLs just cause a messy can't access > http:443 message when they are blocked. Have you found any way to > tidy that up?? > > -- > > Brian Gregory. > [EMAIL PROTECTED] > > Computer Room Volunteer. > Therapy Centre. > Prospect Park Hospital. ------- End of Original Message -------
