Re: [squid-users] disk replacement algo source code

Each on-disk object has a StoreEntry in the memory index. When the
StoreEntry is removed, so is the on-disk object.

--
Henrik Nordstrom
Squid Hacker
Sadhna.Ahuja@nokia.com wrote:
> 
> Hi Henrik,
>         I understand how the replacement policies work on the in-memory
> objects and StoreEntry's. What I don't understand is how (where in the src
> code) is this situation handled -- Say, I have configured my Squid to use a
> 'cache-dir' of 100MB. All of this has been filled, but none of the content
> has expired, hence not been flushed out by 'swapMaintainSpace'. What happens
> if a new file needs to be opened on the filesystem for new incoming content?
>         If my understanding so far is correct, StoreEntry is just a sort of
> index in memory for objects on the disk, and releasing a StoreEntry doesn't
> effect the actual stored object. Am I right?
> 
> Thanks,
> Sadhna.