Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!msi.umn.edu!molenda From: molenda@s1.msi.umn.edu (Jason Molenda) Newsgroups: news.software.b Subject: Re: *SERIOUS* expire problem... Keywords: help! Message-ID: <1991Mar8.063951.8673@s1.msi.umn.edu> Date: 8 Mar 91 06:39:51 GMT References: <1991Mar8.015811.243@fs7.ece.cmu.edu> <1991Mar8.041513.5491@s1.msi.umn.edu> Organization: Minnesota Supercomputer Institute Lines: 28 molenda@s1.msi.umn.edu (Jason Molenda) writes: >george@taca.ece.cmu.edu (George Cebulka) writes: >> I'm having a problem with articles not getting expired. [...] >The easiest solution is to run 'addmissing' if you are running a >Alternatively, run a manual find(1) to delete messages older than >days and delete them. My thinking cap wasn't on. There is a third (rather undesirable) option. You can rebuild your history file. It really isn't _that_ bad on most systems these days; just set up an atjob to do it at some obscenely late hour of the night and you probably won't even notice. The only drawback is that you have increased chances of getting slightly-old articles at your site that have already been expired but would have still been in the history file normally. Not usually a big problem because your neighbour sites will usually 'shield' you from any serious problems with older articles. (to an extent.. it isn't Good Policy to rely on your neighbours to keep their expired Message-IDs around a long time.) -- More information that you couldn't have existed another day without, from: Jason Molenda, Tech Support, Iris & News Admin, Minnesota Supercomputer Inst molenda@s1.msi.umn.edu || molenda%msi.umn.edu@umnacvx.bitnet "And remember: Evil will always prevail, because Good is dumb." -- Spaceballs