On 24-Tam-02, Matt wrote:
> If it is not being culled properly then I can only assume that the cache > pruner is not running. I'm not entirely sure how it determines the > last time it ran.. but it is certainly dependent on a proper shutdown. Ah, ok. It's no wonder then that during 15 days (or whatever the default time between cleanups is) V manages to collect a lot of stuff. I just find it annoying when V prunes the cache, as it takes a lot of CPU time to access the hard drive and things slow down, so I haven't changed it to anything smaller. > If you run the cache pruner now, does it say that the cache size was not > the same as it expected? This means somehow the size is not being > tracked properly.. note that V needs to know the real cache size and > THEN shut down properly on exit (so, run the cache pruner, click > "prune" and then shut down).. I think it has complained about wrong estimated size every time I have run it :-) > .. anyway, it's a very confusing system. As someone said, it's actually > quicker sometimes to completely disable the cache completely. Yes, and this I did. _____________________________________________________________________ Voyager Mailing List - http://v3.vapor.com/ Voyager FAQ....: http://faq.vapor.com/voyager/ Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
