[…]
> client<->squid : 31Mbps.
[…]
> Squid<->server : 28Mbps
>
> Total: 59Mbps.
>
> Which is slightly higher than the known "good" performance limit for
> Squid-3.1. Which is up to ~50Mbps, tuning both in Squid and the system can
> reach around 100Mbps IIRC. But that sort of numbers you are
On 27/03/2013 6:09 a.m., Youssef Ghorbal wrote:
the cachemanager can be usefull to see the actual activity of your squid :
squidclient localhost mgr:5min
gives you the last 5 min stats. (see if the n° of req/s is coherent
with what you expect )
Here after the output of the mgr:5min
It show th
Consider this, you do not need dansguardian to use
blacklists. I know thats not really addressing your issue, I just
thought I would mention it since I host http://squidblacklist.org
-
Signed,
Fix Nichols
http://www.squidblacklist.org
On Mar 26, 2013, at 1:19 PM, Youssef Ghorbal wrote:
> Hello,
>
> We have a Squid 3.1.23 running on a FreeBSD 8.3 (amd64)
> The proxy is used to handle web access for ~2500 workstations and in
> pure proxy/filter (squidGaurd) mode with no cache (all disk caching is
> disabled)
>
>> the cachemanager can be usefull to see the actual activity of your squid :
>>
>> squidclient localhost mgr:5min
>>
>> gives you the last 5 min stats. (see if the n° of req/s is coherent
>> with what you expect )
>
>
> Here after the output of the mgr:5min
> It show that we are around 168 req
On Mar 26, 2013, at 1:33 PM, Alexandre Chappaz
wrote:
> Hi,
>
> you can activate the full debug
> launch
> squid -k debug
> with the service running, and check what comes in the cache.log.
I'll give it a try.
How to stop debug by the way ? just squid -k debug again ?
>
> squid -k parse will
The current FreeBSD ports available for squid are squid31 and squid32
I'll be able to upgrade to the latest 3.2 but not further.
Youssef
-
On Mar 26, 2013, at 1:50 PM, Amos Jeffries wrote:
> The first step in debugging any problem like this is to upgrade to the latest
> version
On Mar 26, 2013, at 1:50 PM, FredB wrote:
>
> Are you using delay_pool ?
Nope, we are not using delay_pools.
The first step in debugging any problem like this is to upgrade to the
latest version and see if it has been resolved.
The current latest is Squid-3.3.3.
Amos
On 27/03/2013 1:33 a.m., Alexandre Chappaz wrote:
Hi,
you can activate the full debug
launch
squid -k debug
with the service running,
Are you using delay_pool ?
Hi,
you can activate the full debug
launch
squid -k debug
with the service running, and check what comes in the cache.log.
squid -k parse will audit your config file. Look for WARNING in the
output of this command.
the cachemanager can be usefull to see the actual activity of your squid :
squid
Hello,
We have a Squid 3.1.23 running on a FreeBSD 8.3 (amd64)
The proxy is used to handle web access for ~2500 workstations and in
pure proxy/filter (squidGaurd) mode with no cache (all disk caching is disabled)
It's not a tranparent/intercepting proxy, just a plain expli
12 matches
Mail list logo
