Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!dayton!meccts!meccsd!mecc!sewilco From: sewilco@mecc.MECC.COM (Scot E. Wilcoxon) Newsgroups: news.software.b Subject: Re: Is the history file really needed anymore? Message-ID: <846@mecc.MECC.COM> Date: Thu, 22-Jan-87 11:58:06 EST Article-I.D.: mecc.846 Posted: Thu Jan 22 11:58:06 1987 Date-Received: Fri, 23-Jan-87 23:49:57 EST References: <5504@ukma.ms.uky.csnet> <1307@ncr-sd.UUCP> <825@mecc.MECC.COM> <3831@sdcrdcf.UUCP> Sender: news@mecc.MECC.COM Reply-To: sewilco@mecc.UUCP (Scot E. Wilcoxon) Organization: Minn Ed Comp Corp, St. Paul Lines: 24 Summary: How to keep track of Message-IDs of expired articles? In article <3831@sdcrdcf.UUCP> lwall@sdcrdcf.UUCP (Larry Wall) writes: >In article <825@mecc.MECC.COM> sewilco@mecc.UUCP (Scot E. Wilcoxon) writes: >>Aren't we talking about an awful lot of inodes here? >No. These are links to already existing articles. Only the new subdirectories >would need new inodes. I apparently was trying too hard to be brief. I meant for the expired articles, not just the current ones. Many sites seem to keep articles for 3-7 days, and history entries for 1-4 weeks. As previous posters have said, an expired article would have to keep some kind of 'file' for a Message-ID entry until the 1-4 week period expired. I have since realized that all expired articles could point to the same file, perhaps one simply saying "Expired Article." Similar ideas are to have one such file for each day ("Expires: somedate"), and for the file to contain a list of Message-IDs which expire on that date (expire just has to find the file, then delete everything on the list). Remember I'm talking about articles for which expire has already deleted the text, and just needs to keep track of the Message-ID for a while. -- Scot E. Wilcoxon Minn Ed Comp Corp {quest,dayton,meccts}!mecc!sewilco (612)481-3507 sewilco@MECC.COM ihnp4!meccts!mecc!sewilco "Who's that lurking over there? Is that Merv Griffin?"