Re: wwwoffle -purge doesn't clean cache

> > On 10.09 14:02, Andrew M. Bishop wrote:
> > > I think that the problem is caused by the fact that you have got the
> > > 'age' option set to -1.  This means not to delete pages even if they
> > > are old.  I think that what happens in this case is that the purging
> > > to free up space is not working either.

On 13.09 19:03, Andrew M. Bishop wrote:
> When I answered your previous e-mail I read the purge.c source code to
> work out what might have gone wrong.  This time I have read the
> documentation and I find that I had thought about this before.  It
> does say that URLs that are marked not to be purged will not be.
...
> max-size = (size)
...
> min-free = (size)
...

> After reconsidering the options (leave it as it is or change so that
> the max-size/min-free options take priority) I have decided that I
> will leave it as it is.  There may be people that rely on it working
> the way that it does.  Certainly if people are using WWWOFFLE as a
> permanent cache then if they have set an age of -1 to never delete a
> cached file they should be able to expect that it will never be
> deleted.

Pardon me, the max-size and min-free were not my problem. The problem was
in the "age=-1" which caused "not to delete". Previous setting "age=0"
caused "not to keep" and I have no option "ignore age, use others".

Actually, I think it would be better to use "-1" for each one as "don't
consider this one", in which case "don't delete" would be configurable by
setting all options "max-size", "min-free" and "age" to "-1".

Other possibility is to use age of "0" as "don't consider", because "don't
keep" is already covered by DontCache section.

-- 
Matus UHLAR - fantomas, [email protected] ; 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.
Micro$oft random number generator: 0, 0, 0, 4.33e+67, 0, 0, 0...