Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pacbell!cpro!asgard From: asgard@cpro.uucp (J.R. Stoner) Newsgroups: news.software.b Subject: Re: Dbz and news 2.11 Message-ID: <59@cpro.UUCP> Date: 5 Feb 89 22:26:41 GMT References: <373@twwells.uucp> Distribution: usa Organization: COG Gateway, Hayward, CA Lines: 33 From article <373@twwells.uucp>, (T. William Wells): ; In article <5095@b-tech.ann-arbor.mi.us> (Jon Zeeff) writes: ; : As the author, I suppose I can supply an authorative answer. Dbz ; : contains no AT&T code at all. The only thing in it not written by me ; : is the hashing, and that is taken from pathalias (with permission). ; : Here it is if anyone missed it: ; : dbz.c V1.5 [ Code elided ] ; Any reason I should switch from 1.3? Before you respond maybe you can address a concern of mine that has to do with dbz 1.3 and possibly dbz 1.5 to wit: I had previously been using dbz 1.3 with 2.11.13 news to speed up the news system (which it did) but started seeing problems with expire when the history file grew past some as yet unidentified boundary. It seems that the files are properly removed at the expiration time but the reconstructed history file seemed to increasingly have nulls in front of the first line. Needless to say, before I increased my ulimit (a Microport SysV/AT 2.2) to something reasonable the history file would then not stay within bounds and get truncated. I liked the speedup but did not like having to blow off the history file and reconstruct it by hand periodically. If this is a known problem that is addressed in 1.5 then I would want to re-install dbz (also hoping it will work with C news or whatever is coming down since B news is about to end). If this is something I did wrong in my localize.sh then maybe some sample of the right thing to do would be appreciated. -- "To prevent having to tell fools to RTFM don't let on you WTFM in the first place." - J.R. (May the Source be With You) Stoner asgard@cpro.uucp asgard@wotan.uucp asgard@well.uucp ...decwrl!pacbell!cpro!asgard