Newsgroups: news.software.b
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: 2.11.19 w/dbz help request
Message-ID: <1990Apr9.163726.26306@utzoo.uucp>
Organization: U of Toronto Zoology
References: <16025@obdient.chi.il.us>
Date: Mon, 9 Apr 90 16:37:26 GMT

In article <16025@obdient.chi.il.us> blair@obdient.chi.il.us (Doug Blair) writes:
>A few weeks ago I recompiled with dbz...
>Just a couple days ago I realized that we had been getting duplicate
>articles from two sites and that both had been added to the article
>directories. The message ID's appear to be identical....

The two common reasons for this are (a) you compiled dbz with INCORE set
and something isn't doing dbmclose() to flush the results out to disk,
or (b) dbz and the news software disagree on case-mapping policy.

It is a waste to use INCORE on anything that isn't doing a lot of database
accesses.  We don't use it for C News relaynews, and the less said about
B News the better.  The real customer for INCORE is expire.

(You ought to put dbmclose() calls in the right places anyway, but avoiding
INCORE is a good stopgap.)

Check whether your dbz is compiled with CNEWS, rather than BNEWS, defined
in the source.  Late-model B Newses, for some reason, decided to treat
message-IDs as case-insensitive, while C News goes whole hog and implements
(approximately) the proper RFC822 case-sensitivity rules for message-IDs.
The difference matters to dbz.

(We would be happier, and the software would be more efficient, with the
old case-sensitive policy, but the genie is out of the bottle now... :-()
-- 
Apollo @ 8yrs: one small step.|     Henry Spencer at U of Toronto Zoology
Space station @ 8yrs:        .| uunet!attcan!utzoo!henry henry@zoo.toronto.edu
