So, which would it imply if one finds a system with a 1 GB history file; 1) that the system does not rebuild the history file very often, or 2) that the system probably does a huge volume of news and cannot rebuild the history file often enough to keep the file resonably sized? Or, 3) other (please explain)?
Chris Caputo wrote:
The size of the history file is not necessarily related to the amount of news held. This is because many history files contain message-ids for articles held in the past, long after they have expired off of the spool.
Some sites have 30 day history files even though they only hold articles for 10 days. As an example our history file currently contains:
Articles retained 3086663 Old entries retained 3342562
There are actually more lines devoted to message ids from the past than ones currently on the spool.
Chris
On Thu, 19 Jun 1997, Kenneth Whittaker wrote:
I would not recommend that. I am guaging the sizes of the spools, directories, etc. The size of the history file seems to be a pretty good measure of the volume of news you are handling. Albiet, some people try to avoid rebuilding the history file by deleting the spool, but I don't know how much that buys us if the deletions themselves could be expensive.
I am assumeing the history files are not on the filer.
-- Kenneth Whittaker Network Appliance Technical Support: 888-4-NETAPP