Thanks for the link Aaron - that looks very interesting. In this case, the issue was caused by the cron process calling http://localhost/cron.php instead of http://[domain name]/cron.php
Boost uses the host in the request address to determine which directory to expire cached pages from. In this case, no localhost' directory existed in the cache dir, so no pages were expired. Running cron via the browser worked (dropped cache from 1.3Gb to 288Mb) and getting the dev to alter the crontab entry to use the full domain name has had the desired effect also. For those running (and caching) high-traffic, multi-lingual Drupal sites you may also want to take look at this: http://drupal.org/node/174380 :) Paul --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
