Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!umich!dgsi!brian From: brian@cimage.com (Brian Kelley) Newsgroups: news.software.b Subject: Re: Cnews expire problems Message-ID: <1991Feb20.195229.10997@cimage.com> Date: 20 Feb 91 19:52:29 GMT References: <1991Feb20.161636.9861@cimage.com> Reply-To: brian@dgsi.UUCP (Brian Kelley) Organization: Cimage Corp, Ann Arbor, MI Lines: 38 In article <1991Feb20.161636.9861@cimage.com> brian@cimage.com (Brian Kelley) writes: >My question is, why are those old articles hanging around? I did have some >problems (I believe back in Jan) running low on space. doexpire couldn't >find space for it's work files. I don't believe that expire failing back >then should effect last night's expire (which ran fine and should have >removed those articles). Any thoughts? Ok, problem solved. When the Cnews expire runs, looking for articles to kill, it looks at the entries in the history file. It does not traverse the file system. Back in January, expire ran out of space a couple of times. I believe the history file wasn't properly updated and therefore the articles were never expired. The solution was to run mkhistory to rebuild the history file based on what is actually in the news spool directory. Simple. Though when I ran mkhistory, I got the following message: mkhistory: found in history.n -- aborting Cute, eh? I took the brute force approach and edited the history.n file, deleting the offending swill line (and removing the two articles it had a problem with by hand). I am going to complete the remainder of the mkhistory script by hand. Hopefully tonight expire will do the right thing and all will be well. Thanks to the two very quick respondents who clued me in to the mkhistory solution. Brian --- brian@cimage.com