Re: [squid-users] maximum_object_size > 2GB prevents caching?

On 17.05 09:31, Denis Vlasenko wrote:
> On Friday 14 May 2004 15:04, Christoph Haas wrote:
> > this morning we found out that our cache hit ratio is zero. We started to
> > investigate and according to the store.log all objects were tagged
> > "RELEASE". There were absolutely no files cached in the cache_dir.
> >
> > We reduced the squid.conf to track down the problem. It appears that when
> > specifying a maximum_object_size larger than 2 GB the whole caching feature
> > becomes disabled. However I haven't seen anything useful in the cache.log
> > that would give me a hint.
>
> if maximum_object_size is a 32 bit signed int, >2GB turns into negative number.
> Certainly, it can be made 64 bit, but why do you want maximum_object_size
> that large?!

he said it was a mistake. However if someone wants squid to be able to
cache DVD images...

Changing maximum_object_size to long long (or however is it called, iirc
quad on FreeBSD) wouldn't help itself. Squid should be rewritten to use
64bit file access. squid 3.0 supports it for now.

-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Eagles may soar, but weasels don't get sucked into jet engines.