On Mon, Nov 21, 2011 at 10:35 PM, Amos Jeffries wrote:
Also in the squid.conf:
acl toSquirm url_regex ^http://www\.google\..*/(search|images)\?
url_rewrite_access allow toSquirm
url_rewrite_access deny all
... will make Squid not even bother to send URLs to Squirm if they wont be
Thanks Amos.
As for the title question: You are the only one who knows that. It depends
entirely on how much RAM your system has and how much is being used (by
everything running). The number which can run on your system alongside Squid
and the OS and everything else without causing the
On Mon, 21 Nov 2011 16:44:04 +0100, Leonardo wrote:
snip
I'd also look at what Squirm is doing and try to reduce a few things
...
* the number of helper lookups. With url_rewrite_access directive
ACLs
* the work Squid does handling responses. By sending empty response
back
for no-change, and
Dear all,
I have a Squid transparent proxy which uses 40 Squirm URL rewriter
processes. Everything worked fine until today, when Squid crashed
after an error 179 pending requests queued:
2011/11/15 13:55:41| WARNING: All redirector processes are busy.
2011/11/15 13:55:41| WARNING: 40 pending
On Tue, 15 Nov 2011 16:59:46 +0100, Leonardo wrote:
Dear all,
As for the title question: You are the only one who knows that. It
depends entirely on how much RAM your system has and how much is being
used (by everything running). The number which can run on your system
alongside Squid and
