Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!ambar
From: ambar@bloom-beacon.mit.edu (Jean Marie Diaz)
Newsgroups: news.software.b
Subject: Re: expire problem in bnews 2.11.18
Message-ID: <AMBAR.89Sep17224754@hodge.MIT.EDU>
Date: 18 Sep 89 02:47:54 GMT
References: <53@lad.sdl.UUCP> <839@lilink.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: Madhouse International Technologies
Lines: 23
In-reply-to: tbetz@lilink.UUCP's message of 16 Sep 89 21:50:32 GMT


   From: tbetz@lilink.UUCP (Tom Betz)
   Date: 16 Sep 89 21:50:32 GMT

   It's now reporting "2576768 unread articles in misc.jobs.resumes"
   when I have done an 'expire -i0 -I21 -r' to clean up the message
   base and start over, and there are exactly 0 articles there....
   but still rn is having to seek forever  to find this out.

   Is there a way to invoke rn so that it will catch up all
   newsgroups? 

This isn't rn's problem, this is expire's problem.

If you read the code, you will note that expire reads the max field from
the active file, and unless min > max or an-article-number > max, it
never gets changed.

What we did here was to turn off news; run a emacs macro over the active
file to convert all the min and max fields to 0000000, and then run
expire -u, which updated the active file correctly.

				AMBAR