Hi,
Any news on this topic? Unfortunately, RAM is running full within days
and at the moment, our workaround is to do a reboot ... We would
appreciate any other solution!
thanks,
peter
On Wed, May 11, 2011 at 3:47 PM, guest01 gues...@gmail.com wrote:
On Wed, May 11, 2011 at 10:47 AM, Amos
On 30/05/11 20:07, guest01 wrote:
Hi,
Any news on this topic? Unfortunately, RAM is running full within days
and at the moment, our workaround is to do a reboot ... We would
appreciate any other solution!
thanks,
peter
:) I was just looking at this bug again today.
:( still no seriously
ok, I can at least try to start it under valgrind, which I have never
heard before. Do I just start squid under valgrind and send you the
logfile? Do you need any special options?
On Mon, May 30, 2011 at 2:15 PM, Amos Jeffries squ...@treenet.co.nz wrote:
On 30/05/11 20:07, guest01 wrote:
Hi,
On 31/05/11 03:20, guest01 wrote:
ok, I can at least try to start it under valgrind, which I have never
heard before. Do I just start squid under valgrind and send you the
logfile? Do you need any special options?
Squid need valgrind support built in when this is done.
Apart from that yes it
Hi,
I am currently using squid 3.1.12 as forward-proxy without
harddisk-caching (only RAM is used for caching). Each server is
running on RHEL5.5 and is pretty strong (16 CPUs, 28GB RAM), but each
servers starts swapping a few days after start. The workaround at the
moment is to reboot the server
On 11/05/11 19:19, guest01 wrote:
Hi,
I am currently using squid 3.1.12 as forward-proxy without
harddisk-caching (only RAM is used for caching). Each server is
running on RHEL5.5 and is pretty strong (16 CPUs, 28GB RAM), but each
servers starts swapping a few days after start. The workaround
