> I run nntpcached -e every so often. I've just upgraded to 1.0.5 from some > really old pre-1.0 version, so I'm not sure if the cache expiration is > automatic now (or was it before, I don't think so...). > > On Tue, 25 Mar 1997, Paul Howard-Beard wrote: > > I have the same thing. Please let me know if you find a solution. > > > > -----Original Message----- > > From: nntpcache-users-request@suburbia.net > > Subject: NNTPC: NNTPCACHE keeps growing > > > > The size of our cache keeps growing. It's almost up to 2GB, and > Expiration should be automatic, it is controlled by the following in the config file: # expire if there are under this number of blocks in the cache partition minBlocksFree 1000 # run expire if there are under this number of inodes in the cache partition minFilesFree 1000 # don't let the history file grow larger than this (bytes) hisHighWater 60M # when it does, trim it back to this (bytes) hisLowWater 40M # When we do an expire, kill articles older than this maxArtAge 2w # check disk space, etc for automatic expiry this often # (but only after a client connects or disconnects) expireCheckPeriod 5m The important point that isn't made clear here is that expire runs only occur when minBlocksFree or minFilesFree are not satisfied. i.e the cache will happily grow until the disk starts filling up. Cache expiration isn't incredibly intelligent, although it is very fast and tries to track the actual state of affairs on the remote server. When I finish my active-pre-caching modifications this symmetry will probably be broken and we may have to introduce more complex expiration rules. Cheers, Julian. -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@suburbia.net |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery
