On 11/03/11 07:03, Edward Ting wrote:
Hi Amos,
I read the Bugzilla thread and found the patch may not work for 3.0
since 3.1 has changed its implementaion using reader callback. (Also
mentioned by Alex.)
Any advice how to apply the patch to 3.0?
No sorry, I don't. 3.0 has a great many bugs an
On 10/03/11 18:54, Víctor José Hernández Gómez wrote:
I have found a message such as:
FATAL: xcalloc: Unable to allocate 1 blocks of 536870912 bytes!
Looks like a strange big block.
My squid versión is 3.1.9. Any suggestion?
Probably bug http://bugs.squid-cache.org/show_bug.cgi?id=3113
Ple
Hi Amos,
I read the Bugzilla thread and found the patch may not work for 3.0
since 3.1 has changed its implementaion using reader callback. (Also
mentioned by Alex.)
Any advice how to apply the patch to 3.0?
In 3.0 it does reading(true) before makeSpaceAvailable(); If I do
"maybeMakeSpaceAvailab
I have found a message such as:
FATAL: xcalloc: Unable to allocate 1 blocks of 536870912 bytes!
Looks like a strange big block.
My squid versión is 3.1.9. Any suggestion?
Probably bug http://bugs.squid-cache.org/show_bug.cgi?id=3113
Please try an upgrade to 3.1.11 to resolve that and a few
On Tue, 08 Mar 2011 18:38:42 +0100, Víctor José Hernández Gómez wrote:
Hi all,
I have found a message such as:
FATAL: xcalloc: Unable to allocate 1 blocks of 536870912 bytes!
Looks like a strange big block.
My squid versión is 3.1.9. Any suggestion?
Probably bug http://bugs.squid-cache.org/s
Hi all,
I have found a message such as:
FATAL: xcalloc: Unable to allocate 1 blocks of 536870912 bytes!
Looks like a strange big block.
My squid versión is 3.1.9. Any suggestion?
Regards,
--
Víctor Hernández
Centro de Informatica y Comunicaciones