files purged from cache way before min cache lifetime, ignoring disabled purging

It's been an issue for some time actually, it's one of the reasons why boost is still in alpha. Have you tried today's latest dev version (requires new rewrite rules). In there is this latest patch http://drupal.org/node/413908#comment-1641552 which keeps the cache. Theres still a lot of work to on boost, but I think we are getting closer to it behaving how you would expect it. One thing that boost needs badly with this latest patch is a "maximum cache lifetime", because the files will be there indefinitely with this patch now.

Ripped-out the callback part of _boost_rmdir_rf() since it never worked AFAIK. Here's a patch that should make file expiration work as advertised. Reason this wasn't fixed with the original 6.x port had to do with symlinks.

committed

Hi, first of all thanks a lot for the great module! Is it possible to only purge the cache folder until something changes in the page or the page is updated, and NOT purge the cache at every cron run when nothing has changed in the page?

@mclaren
Set the Minimum cache lifetime to something like 4 weeks so the cache only gets flushed every 4 weeks. It's very hard to set triggers and correctly figure out that a change on 'page A' requires 'page Q' to be flushed as well.
#479942: on node update, update associated term page caches as well
#453908: Hook for panel node types - expiration of static cache; panel containing multiple nodes

It really depends on your site, how it is setup. Nodes work like you requested (edit & save flushes cache) in boost already (boost_nodeapi()), other content types are not there yet.

@mikeytown2
Thank you for reply! I understand the difficulty to catch the triggers from so many modules. I have aggregator, panels, views, quicktabs in my site. I just installed boost today, when I saw the beta rolled out. For now I have set the minimum cache expiration to 4 weeks as you suggested, and will see how it affects the pages other than nodes. Thanks !