ons 2006-08-02 klockan 15:32 -0400 skrev Dave Mullen: > 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. The standard redirector interface is a bit inefficient and you need a number of children depending on your load, or else Squid will consider the helper overloaded and get very upset.. If you are worried about performance then I would recommend you to try looking into using Squid acl's instead. Give you nearly the same pover at only a fraction of the per request performance penalty. Note: In both Squid and SquidGuard you should avoid regex patterns as much as possible. Use structured acl types such as dstdomain. > 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. You probably haven't build the SquidGuard DB files.. see the SquidGuard documentation on how to use DB files which radically speeds up startup and reduces memory usage considerably for large lists. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
