Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!psuvax1!gatech!mcdchg!ddsw1!karl From: karl@ddsw1.MCS.COM (Karl Denninger) Newsgroups: news.software.b Subject: Re: dbz caveat Summary: Lcasing is set correctly. Keywords: dbz runtime Message-ID: <1989Sep29.020320.3841@ddsw1.MCS.COM> Date: 29 Sep 89 02:03:20 GMT References: <1139@svx.SV.DG.COM> <1989Sep26.223014.13868@ddsw1.MCS.COM> <9668@b-tech.ann-arbor.mi.us> Reply-To: karl@ddsw1.MCS.COM (Karl Denninger) Organization: Macro Computer Solutions, Inc., Mundelein, IL Lines: 29 In article <9668@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes: >>Dbz also appears to have a nasty habit of not noticing if you have a >>duplicate under some conditions. That is, articles which are still in the >>history file at times show up again if they are received twice! >> >>This didn't start happening until we changed to dbz from dbm. Is there a >>fix for it? We're running "C" News.... > >Do you have the lowercasing of article ids set right? Can anyone confirm >this? Sure do. We're using dbz 1.5; I got the new one in the mail from you, but it is missing the ".h" file.... thus I can't compile that one. I have changed the "LIMIT" parameter to something really gross (1000003L as suggested) from the default and rebuilt the history (again). We'll see if the problem disappears. We did have somewhere in the area of 70k entries in there before.... Also on the "strange" list: A number of articles that should have expired did not. It would appear that history entries are being lost rather than simply overwritten! -- Karl Denninger (karl@ddsw1.MCS.COM,!ddsw1!karl) Public Access Data Line: [+1 312 566-8911], Voice: [+1 312 566-8910] Macro Computer Solutions, Inc. "Quality Solutions at a Fair Price"