http://qs321.pair.com?node_id=417594


in reply to Apache::CacheContent and unforeseen side effects

One solution would be to ditch Apache::CacheContent and modify the code in your mod_perl handler to use something like Cache::Cache which will only put so many files into one directory before creating subdirectories (if you appropriately set the cache_depth option for Cache::FileCache).
  • Comment on Re: Apache::CacheContent and unforeseen side effects

Replies are listed 'Best First'.
Re^2: Apache::CacheContent and unforeseen side effects
by geektron (Curate) on Dec 27, 2004 at 18:12 UTC
    i'm getting there. Apache::CacheContent doesn't expire files, it seems, if the user hasn't revisited the content in the DefaultTTL time ...
      Ah. Could you setup a cron job to manually "expire" (aka, delete) the old files?
        i could. i'm trying to delete them now, but i can't believe i've forgotten the gnu `find` syntax for the -exec args.

        just trying to get rid of some of them NOW ...