ion possible to help resolve
this issue. Hopefully this is a good start.
cache.log = http://filebin.ca/29vS8jkEfskt/cache.log
squid -v:
Squid Cache: Version 3.5.6-20150725-r13869
Service Name: squid
configure options: '--prefix=/usr' '--exec-prefix=/usr'
'--includ
I did a new install of Squid 3.5.6 and it seems to be working now.
On Fri, Jul 24, 2015 at 7:24 PM, James Lay wrote:
> On Fri, 2015-07-24 at 19:15 -0500, Stanford Prescott wrote:
>
> Thanks for that. Any ideas why I am experiencing that?
>
>
> Stan
>
>
>
> On Fri, Jul 24, 2015 at 7:07 PM, Jam
I may concur with the way it is.
For shared memory, if it is created by worker, it might trigger a race
condition. Also, the size of shared segment is fixed across all processes, so
each worker cannot create a different size of shared memory. So the current
code simply lets master process creat
On 07/25/2015 05:25 AM, Jens Offenbach wrote:
Thanks a lot for your comprehensive testing. Now we are sure that the issue is
independent of the underlying OS.
I can easily reduce the maximum_object_size_in_memory. I have some constraints
from our IT at the moment. I am confronted with a very
Any one ??
On 25 July 2015 at 11:14, Jagannath Naidu <
jagannath.na...@fosteringlinux.com> wrote:
>
> Thanks mike.
> But I think Amos is right.
>
> On 25 July 2015 at 00:27, Mike wrote:
>
>> I see a few issues.
>>
>> 1. The report from the log shows a 192.168.*.* address, common LAN IP
>>
Thanks a lot for your comprehensive testing. Now we are sure that the issue is
independent of the underlying OS.
I can easily reduce the maximum_object_size_in_memory. I have some constraints
from our IT at the moment. I am confronted with a very bad disk IO in our
BladeCenter, so I am forced t
