You have to perform "squidGuard -C all" once. This builds the database for squidguard. Dont perform "squidGuard -C all" before every starting of squid! You should repeat "squidGuard -C all" rebuilding the database if the your blacklist changes. Mit freundlichem Gruß/Yours sincerely Werner Rost GMT-FIR - Netzwerk ZF Boge Elastmetall GmbH Friesdorfer Str. 175 53175 Bonn Deutschland/Germany Telefon/Phone +49 228 3825 - 420 Telefax/Fax +49 228 3825 - 398 werner.rost@xxxxxx -----Ursprüngliche Nachricht----- Von: Dave Mullen [mailto:squid@xxxxxxxxxx] Gesendet: Freitag, 4. August 2006 00:20 An: squid-users@xxxxxxxxxxxxxxx Betreff: Re: squid -> squidGuard: Redirect_children best practice? 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" <brian.gregory05@xxxxxxxxxxxxx> To: "Dave Mullen" <squid@xxxxxxxxxx>, <squid-users@xxxxxxxxxxxxxxx> Sent: Wed, 2 Aug 2006 22:57:11 +0100 Subject: Re: squid -> squidGuard: Redirect_children best practice? > ----- Original Message ----- > From: "Dave Mullen" <squid@xxxxxxxxxx> > To: <squid-users@xxxxxxxxxxxxxxx> > Sent: Wednesday, August 02, 2006 8:32 PM > Subject: 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. > brian.gregory05@xxxxxxxxxxxxx > > Computer Room Volunteer. > Therapy Centre. > Prospect Park Hospital. ------- End of Original Message -------
